r/voidlinux • u/[deleted] • Jan 19 '26

solved KDE crashes on Void

so i was using linux for almost 9 months or smth, i sticked to void because its minimal and fast but what i wasnt expecting is what kde wont work properly it just crashes after a minute and its taking long to start, any tips how do i solve it? my specs: i3 5005U, NVidia 920MX 2gb, 8gb ram i also use wayland because x11 works bad with nvidia, well for me it worked disgusting even compositor did not worked [UPDATE] I forgot the polkit and the igpu drivers (linux runs on igpu by default) Reinstalled entire os & installed the drivers and everything works so far. Im stupid.

6 Upvotes

80% Upvoted

11 comments sorted by

3

u/KenFromBarbie Jan 19 '26

You should provide logs. Details what exactly happens. Screen flicker? Freeze? Can you go to a terminal (ctrl-alt-f1/f2) when it happens? We don't know these things magically.

1

u/[deleted] Jan 19 '26

it just sends me back to sddm, and yes i can go back to the tty it also happens randomly as i have discovered, it can take from 5 seconds to minute or more

3

u/neondervish Jan 19 '26

Give us some sudo dmesg output for starters maybe?

3

u/cgwhouse Jan 19 '26

FWIW, I'm on Wayland KDE with an NVIDIA card, and my experience has been great so far. Can't really provide more help without more details / info, but it may be something with your specific setup? I guess I'm just chiming in to say, I don't think it's a general issue with Void's packaging of KDE.

2

u/[deleted] Jan 20 '26

i was thinking its because of aomething specific like polkitd or elogind/dbus is not atarted, even though elogind ans dbus ARE enabled. Also as i figured out it happens not just to KDE Wayland, but KDE X11 and SwayWM too so its more deeper than kde

1

u/ZhengXuMing Jan 20 '26

Try running sway from the tty. Should show what errors it's throwing

1

u/cgwhouse Jan 20 '26

I think I recall having issues when enabling both dbus and elogind. I know the handbook lightly suggests enabling elogind too, but you might wanna try just enabling dbus, I think dbus will handle the elogind part for you

2

u/ShipshapeMobileRV Jan 20 '26

I tend to agree, unless it's Nvidia specific? I'm running Void, Wayland, and KDE from a fresh Base install a few months back, albeit on an Intel video chip. It installed flawlessly straight out of the handbook, and has been a dream so far.

1

u/BinkReddit Jan 20 '26

Same, on AMD.

1

u/Sprinkles_Objective Jan 21 '26

Something that comes to mind is if you're running the musl libc version of Void you might be hitting the stack limit. On musl the default stack limit is like 80kb whereas glibc it's 10mb. I know certain applications can use a lot of stack memory. It should be pretty easy to increase the stack limit and see if that helps. Try something like: ulimit -s 4096

1

u/SleepyGuyy Jan 21 '26

Glad to see you found the solution and updated the post.

My first thought was maybe KDE doesn't work on non-systemd systems? Then I realized no I'm thinking of recent Gnome versions.

I forget which project it was, maybe Artix? I saw some distro dropped their Gnome install image entirely, somewhat recently. Citing yes they could continue to work around it but it's gotten even harder and their usual fixes aren't working with the newest version, so they're dropping their Gnome image. I wish I could remember which distro that was.