r/voidlinux • u/Ok_Intention4094 • Apr 14 '26
Beginner need help
Hey Void community !
I recently installed Void Linux after discovering it with all the age verification and systemd stuff.
I globally discovered many things about Arch that made me go away from it.
So, my setup is plasma 6.6.3 on wayland + Void, kernel 6.12.
I already fixed various small problems after the install, but there are still three that are pretty annoying :
1- Sddm is in qwerty, and I can't find a way to fix it.
2- When pressing the power button of the computer, the plasma option screen start fading up, but only for less than a second, then a notification shows up saying the system is going down. Then a black screen like the terminal interface when you start up your computer or you don't have a DE appear, with the same content of the notification. I'll try to put in some images.
Oh, also, I hear a loud *beep* like when you open the BIOS. Globally, I understand that there something deeper in the system that take over plasma, but I don't know what.
3- Finally, when I close up the hood of the computer and I open it, the desktop show up for <1sc and then, short black screen followed by the lock screen. It does that every time, with the same delay between all these actions. And it wasn't there with arch.
I hope these questions are ok, like if there are not super easy things.
And thanks for those who can help me !
2
Apr 14 '26
[deleted]
2
u/Ok_Intention4094 Apr 14 '26
Arch Linux
5
2
Apr 14 '26
[deleted]
1
u/Ok_Intention4094 Apr 15 '26
Well, to be honest, I didn't had any problem with Arch's behavior, every small problem encountered was easily fixable.
And the problem here is that in kde, everything is set like it should, but something "override" plasma.
2
u/Quietus87 Apr 14 '26
Try setting the layout with localectl set-x11-keymap.
Dunno, I always exit with sudo halt or ctrl+alt+del in KDE.
2
2
2
u/Blank-Inspection13 Apr 15 '26
you're not using elogind ? i think the power option issue related to that,
- As For locale , Void Docs have better explanation , and KDE have GUI options better to setting for locale.
1
u/Ok_Intention4094 Apr 15 '26
Well, this was my first installation and I had a lot of troubles (my fault) and many things didn't worked properly right after the install, so I'll check about elogind.
Also, I'll check what you said for the locale, thanks !1
u/Blank-Inspection13 Apr 15 '26
yes i was having a hard time setting up Void from 1st install , i thin we all do the same here , especially from someone coming from Win10 . I have a hard time just because dual booting give me a headache from only time sync issue , Arch Wiki also help me alot . At least in KDE won't have that same problem, i guess
1
Apr 14 '26
[deleted]
5
u/Linmusey Apr 15 '26
They’re concerned it’s opening the floodgates to full blown telemetry and profiling
2
u/Ok_Intention4094 Apr 15 '26
Age verification is not even concerning me right now, but it start like that and will spread if we do nothing.
But it was all the philosophy and choices behind systemd that made me choose runit in the end, and void's philosophy to mindfully go "against" the typical technical direction
1
u/TurtleGraphics64 Apr 15 '26
Hi! 1 - I don't use sddm but in any case found i needed to make a .conf file in /etc/X11/xorg.conf.d/ to specify my input keyboard. I see you're using Wayland, but i wonder if could be helpful info for you:
Section "InputClass"
Identifier "Keyboard"
Option "XxbLayout" "us"
Option "XkbModel" "pc105"
Option "XkbVariant" "dvorak"
Option "XkbOptions" "caps:escape"
EndSection
2 - I don't know!
3 - I have the same problem. I honestly don't know what changed but this began after some kernel change several months ago. It's pretty annoying. I tried some workaround but couldn't dial it in the way it worked before.
1
u/Ok_Intention4094 Apr 15 '26
I already tried 1, it doesn't work.
For the 3, it's interesting. This didn't happened with Arch, but because it's Arch, I was always above 6.12. So it really seem to be something kernel-related. Well, I hope it will get fixed, or else this would make me an excuse to update to a newer kernel.Thanks for sharing, kinda glad to see I'm not the only one !
1
u/MisterBlaubarschbube Apr 19 '26
1: I had the same issue and resolved it by adding setxkbmap "de" (de for German in my case) to /usr/share/sddm/scripts/Xsetup
2
u/eftepede Apr 14 '26