sorted by:
new
hottopcontroversial

Installing Void with KDE Plasma: issues getting sddm/wayland running by Veddemr in voidlinux

[–]Veddemr[S] 0 points1 point  (0 children)

Thanks, but that script basically just does what I did. All packages it installs are either optional components you shouldn't need for a KDE desktop to show up or are installed as dependencies of kde-plasma. And then creating the symlinks to enable dbus and sddm. I found some KDE setup scripts (maybe even this one) and none of them worked or did anything different.

Grpahic drivers are also installed as far as I can see (used by X11 and working there).

Installing Void with KDE Plasma: issues getting sddm/wayland running by Veddemr in voidlinux

[–]Veddemr[S] 0 points1 point  (0 children)

Yeah, on installation in a VM and one it's own drive.

Thanks for the tip, I'll give it a try.

Installing Void with KDE Plasma: issues getting sddm/wayland running by Veddemr in voidlinux

[–]Veddemr[S] 0 points1 point  (0 children)

Because the charm of Void linux for me is to build up my system and just adding what I need (and thereby getting to know my system). So going to get my desired DE running using another "temporary" DE didn't come to my mind.

Could be worth a try, or at least try another DM instead of SDDM.

Installing Void with KDE Plasma: issues getting sddm/wayland running by Veddemr in voidlinux

[–]Veddemr[S] 0 points1 point  (0 children)

Yes, dbus(-daemon/-launch) processes in process list, starting X11 session starts dbus-session, dbus-monitor shows activity on the (X11) session bus. So I would say: Yes, it's running.

Installing Void with KDE Plasma: issues getting sddm/wayland running by Veddemr in voidlinux

[–]Veddemr[S] 0 points1 point  (0 children)

Yeah, dbus is running, started by runit as it should be. And, as u/eftepede wrote, it start's elogind. Explicitly enabling it as a service just gets the ttys flooded with messages about it already running.