I didn’t even know that there was a troubleshoot mode. I’ll try and come back here
I didn’t even know that there was a troubleshoot mode. I’ll try and come back here
Hemorragic is not an strain. If you got 1 strain and get recontaminated with a second strain within 6 months, you’ll be in a russian roullete of develop a hemorragic disease
As I said weeks ago: dengue will be a nightmare worldwide. My country, Brazil, has a great plan of action against dengue and 2024 was a disaster cause it was really worse this year.
Take a note: we have free and universal health care, our health system reaches the most remote places inside the country, we have a great vaccination plan, our population takes vaccines, we handle dengue every year very well.
Looks like a runtime is outdated and the repo to install a new runtime is missing. Then when Discover tries to update, crashes cause there is nowhere to download from
Try update the package from terminal
I also think the suggestions in this videos are shitty and impractical.
He’s dreaming about something that could not be implemented. And even if implemented, is just cluncky and unusable.
I just ignored this video. And actually, most of his videos I’m ignoring as well.
I guess you can set a host on your /etc/hosts
to redirect all your pterodactyl.example.com to a local ip. Also, if you need access from other computers on the local network, I think you can set up a local DNS server (such as PiHole or AdGuard Home) to reach the same solution but for all address running though your DNS server
I think Gnome VS KDE it’s just a POV
Your argument makes sense that KDE and Cinnamon can be welcoming to Windows users. However I can argue that it can also make these newcomers to keep a “windows-like” mindset and that can be frustrating.
If a newcomer comes to Gnome, due to it’s totally different paradigm, it may induce this newcomer to have an open mind and, therefore, be more welcoming to linux experience.
I don’t think one argument or the other is right or wrong. I think both arguments are valid and that’s just a different perspective. I, personally, think that a totally new paradigm is good to newcomers, but be free to disagree, since you understand that there is no right or wrong regarding this topic
I like the mint project, but I dislike how it’s done
I don’t suggest mint to anyone anymore. I rather suggest Fedora or PopOs
Já tem 1 ano?
Caraca!!
Parabéns pra nós! Estou aqui desde o comecinho! Minha conta vai fazer 1 ano dia 24 (acabei de ver aqui)!
And did u find out?
To use pacman you must have root permissions. You can do this by using sudo
.
If your installation is correct, you must just use sudo pacman -S kdeplasma-addons
sudo
is a command that escalates your user’s privileges to have root
power
pacman -S
installs a package
I’m glad you solved!
Also, in case you wouldn’t mind helping me with this other thing that is outside the scope of the initial complaint: where do I find the KDE cube options? It doesn’t seem to be in the Window management options, nor do I see a downloadable version of the such. The KDE plasma version is 6.0.5.
Well, I may take a look, but I’m not a KDE user at all. I’m on Gnome for over 5 years already.
Try Settings > Window Management > Desktop Effects > “Windows Management” section > Overview and configure it.
However looks like to make it work, you should have at least 3 virtual desktops.
I suggest you to open a new thread with this question, cause I really don’t know enough about KDE
Not sure what you are suggesting, but it seems that the hard drive is the last active option in the boot order for that VM. I assume you are suggesting to make it the priority boot device?
Exactly
I still don’t know how to switch between the keyboard layouts, and with this installation I opted for the US keyboard layout to be the default one, but have since added one more layout to the list. I couldn’t place the keyboard layout widget for some reason, and there is no indication of what layout is chosen on the SDDM screen at all.
Right now, the user is blocked due to too many attempts to enter password, so I will have to wait.
Read my other comment. Maybe this is the breeze setting that does not have any way to change layout at the logging screen. Also I suggest you to reboot your VM after these changes you made
EDIT 2: I still do not know how to switch between keyboard layouts in SDDM, and I can’t find information regarding that.
It depends on the theme you’re using. Change the file /etc/sddm.conf
and comment the line where KDE is setting the theme. Should be something line
[Theme]
Current=blablabla
ThemesDir=blablabla
Just comment putting a hashtag before these lines
Maybe you have to edit using Vim, Emacs or Nano at the tty
The keyboard layouts should be at the top of the logging screen at the default sddm theme
EDIT: also, Ctrl+Alt+F2 just produces a black screen.
Then try Ctrl+Alt+F1
I don’t know beyond the fact that only Grub got installed and, apparently, nothing else. Upon starting the virtual machine, I was still offered to boot into the Arch installation environment. I have run archinstall again to make an installation without Grub, and am running an installation on a clone of that virtual machine where I have opted into using Grub
It seems like VirtualBox doesn’t automatic removed the iso file from the boot options. Try change this configuration at the VirtualBox and select the boot to be at the virtual driver
Currently, I am not sure how I am supposed to login as root.
At the archinstall script you must’ve set the root password, right? At the SDDM login screen, you must press Ctrl+Alt+F3 to enter the TTY3 (a big whole full screen terminal) asking for a login. Type root
, press enter and then it will ask for your password. Type the password you set in the archinstall script (note: in the terminal we do not have a visual feedback from the password field, but it’s being written. Just trust the process) and press enter. Now you are logged in as root
Where do I input that command?
At the terminal. To access the terminal you must change to TTY3, login as root and run the command I told. To enter TTY3 you must press Ctrl+Alt+F3. To go back to the graphic interface you must go to TTY2, pressing Ctrl+Alt+F2
To which one? What is the format supposed to be for, for example, English, Putonghua, Norwegian, and Russian layouts?
Whatever layout you want. You can find a list with all the layouts running the command # localectl list-x11-keymap-layouts
. I think us
is english, no
is Norwegian and ru
is Russian. So the command would be # localectl set-x11-keymap us,no,ru
The problem is that it is initially not the US English one, while the password is in English.
Well, that’s unfortunately. But try these things I told you
Another installation failed for no discernable reason despite no errors occurring as a result of
archinstall
.
What happened?
Edit: Are you familiar with the syntax of Linux commands? I’ve written # localectl set-x11-keymap us,no,ru
but that means you must run the command localectl set-x11-keymap us,no,ru
as root, okay? The dash symbol (#) means you’re running the command as root, while the dollar symbol ($) means you run a command as non-privileged user, for example echo Hi
you must run the command echo Hi
as your normal user (not as root nor using sudo
)
I did exactly the same thing yesterday and had the same issue. However I found the solution adding the keyboard layout to the X11 as well, with the command
# localectl set-x11-keymap br abnt2
You must change the “br abnt2” to your keyboard layout, however
Also, pay attention because there is a bug at the sddm login screen that doesn’t show the correct keyboard layout until you start typing, so don’t worry if at the beginning is “US”. Just start typing your password and take a look to see if it changed to your keyboard layout
Edit: you may wanna enter TTY3 to make these changes. Just press Ctrl+Alt+F3 to enter TTY3 and after you’re done press Ctrl+Alt+F2 to be back to the previous display. You may wanna also restart your computer
Fuck U.S.
Yes, it does happen in Troubleshoot Mode. And based on the article you sent, it does mean it’s a Firefox issue, not a extension one