@notTheCat there's a technique where you boot with a live system, mount your linux system, chroot into it amd change passwords. If you think this is insecure for your system, then you should considering encrypting at least your home diretory/partition.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
If you CTRL-ALT-F3 and login to a non graphical session does everything work as intended?
Yes everything in TTY works as intended, I can login as my user account and sudo works as it should
That's really weird. I set up a test system and I couldnt reproduce. The only thing I noticed errors flooding dmesg about elogind already running when I enabled it following the docs. I guess sddm is already starting it?
I dont see how that would cause your issue though. I would probably just reinstall lol
I'm starting to suspect my HDD failing at this point, so many weird bugs lately
I do not know how to solve your problem but I suggest posting to c/voidlinux or their subreddit which should have more people capable to help.
Do you have an sddm
user in the sddm
group?
Yes I do
Do you have polkit installed?
Also does startplasma-wayland
or how its called in the TTY work?
Plasma on X11 is practically unmaintained afaik
Yes I have polkit installed
Executing startplasma-wayland returns the following:
startplasmacompositor: Could not start D-Bus, Can you call qdbus?
I don't have an excutable/command named qdbus
I never used Void and think it is meant for people that solve such issues themselves.
I would recommend a distro where even manually installing KDE plasma packages will result in a "just working" Desktop, like Fedora.
Otherwise, contact the Void people.
I did a few minimal installs, currently working on a Qt6-only Wayland-only minimal install to test RAM consumption.
Do have the startx
command installed ? You can use that from the command line without DisplayManager (Switch to a virtual console with e.g. ctrl-alt-F2). And with XFCE4 you can use the command startxfce4
to start from the command line without DisplayManager. This could help troubleshoot.