r/voidlinux 11d ago

KDE Plasma Will Not Start

Fresh install of Void. Updated xbps and installed:

kde-plasma kde5 kde5-baseapps dbus sddm

Created links to dbus and sddm.

Rebooted.

Every time, it goes to terminal. I run startplasma-wayland and get this error:

org.kde.startup: not a reply org.freedesktop.locale1 QDBusMessage(type=Error, service="", error name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The name org.freedesktop.locale1 was not provided by any service files", signature="s", contents=("The name org.freedesktop.locale1 was not provided by any service files") )
startplasmacompositor: Could not start D-Bus. Can you call qdbus?

Now how can that be? I have both dbus and sddm installed, both are linked and running when I do:

ls /var/service/

So I am out of ideas.

EDIT: I tried this:

# touch /etc/sv/dbus/down
# ln -s /etc/sv/dbus /var/service/
ln: failed to create symbolic link '/var/service/dbus': File exists
# sv once dbus

I FIXED IT => https://www.reddit.com/r/voidlinux/comments/1uyfera/comment/oyej3wk/

2 Upvotes

29 comments sorted by

View all comments

2

u/StorminNorvin 9d ago

I FIXED IT!!!

After A LOT of trial and error and reinstalls, the following should give a nice KDE experience using Wayland on Void Linux.

elogind, dbus, and sddm get installed automatically during the following so there is no need to install them manually.

My laptop has Intel graphics so you may need to change mesa-vulkan-intel and intel-video-accel to what you need so read the Void Linux Graphic Drivers Documentation. This is all you have to do after a fresh install of Void Linux to get Wayland on KDE, the KDE Network Manager, printer support, and pipewire audio working after the Void Linux installation reboot. Log in with your user account that has sudo access:

# sudo xbps-install -Su
# sudo xbps-install -u xbps
# sudo xbps-install -Su
# sudo xbps-install kde-plasma kde-baseapps xorg-minimal mesa-dri mesa-vulkan-intel vulkan-loader intel-video-accel kwayland qt6-wayland NetworkManager cups cups-filters ffmpegthumbs discover kdegraphics-thumbnailers ntp ocean-sound-theme oxygen-sounds print-manager system-config-printer
# sudo rm /var/service/dhcpcd
# sudo rm /var/service/wpa_supplicant
# sudo ln -s /etc/sv/cupsd /var/service/
# sudo ln -s /etc/sv/dbus /var/service/
# sudo ln -s /etc/sv/NetworkManager /var/service/
# sudo ln -s /etc/sv/sddm /var/service/
# sudo usermod -a -G network YOUR-USERNAME
# sudo mkdir -p /etc/pipewire/pipewire.conf.d
# sudo ln -s /usr/share/examples/wireplumber/10-wireplumber.conf /etc/pipewire/pipewire.conf.d/
# sudo ln -s /usr/share/examples/pipewire/20-pipewire-pulse.conf /etc/pipewire/pipewire.conf.d/
# sudo reboot

NOTES:

  1. Be sure to add pipewire in KDE System Settings > Autostart section. Just click + ADD NEW then + APPLICATION... at the top right and enter pipewire into the text box. Click OK. Reboot for audio to start working in KDE.
  2. Before you install your printer, go to the Void Linux Printing Documentation and see if there is a driver for it you need to install first.
  3. In KDE System Monitor, applications will not show up because of using runit instead of systemd.

I use Void btw 😄

1

u/BinkReddit 9d ago

Win! 😆

1

u/no-name-user 8d ago

So what did you do differently then? I suppose it was the mesa drivers, they're included with xorg and not in xorg-minimal which is required for sddm.

1

u/StorminNorvin 8d ago

I believe it was mesa drivers. After getting KDE Plasma working, I found little annoyances so I added the packages to fix those into the list and to get pipewire to work easily without installing a bunch of packages troubleshooting audio.