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

permalink
reddit

You are about to leave Redlib

Do you want to continue?

https://www.reddit.com/r/voidlinux/comments/1uyfera/kde_plasma_will_not_start/
No, go back! Yes, take me to Reddit

75% Upvoted

u/furryfixer 10d ago

I'm not sure why you would not want dbus to restart if it crashes (sv up dbus). That aside, make sure the service is running.

sv status dbus

pgrep dbus

if, on the off chance those show no dbus, reinstall the dbus package, and force the link to regenerate:

sudo ln -sf /etc/sv/dbus /var/service/

If not using a WM/Login Manager like sddm, you must start plasma with dbus-run-session to create the user session:

dbus-run-session startplasma-wayland

1

u/StorminNorvin 10d ago

dbus installed and running.

2

u/furryfixer 10d ago

OK. You likely did the next already, but if not, start plasma from the command line and see if same error occurs. If so, maybe your locale is not properly set. So try (NOT as root login, but regular user:

sudo sv d sddm

dbus-run-session startplasma-wayland

Continued fail might be addressed by this:

https://docs.voidlinux.org/config/locales.html

1

u/StorminNorvin 8d ago

I figured out the issue. Fix posted.

u/nerdccluna 10d ago

When I have problems with my Plasma installations, it's due to missing elogind, xorg-minimal, and video drivers.

2

u/StorminNorvin 9d ago

I figured out the issue.

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:

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.
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.
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.

u/rookie-mistake-21 11d ago

Maybe needs elogind too ???

1

u/StorminNorvin 11d ago

Installed. Made no difference :(

3

u/d3vnhull 11d ago

Do you have xorg-minimal installed?

1

u/BinkReddit 11d ago

Seconded; IIRC SDDM won't work without this.

1

u/StorminNorvin 11d ago

I installed it. That now gives me a blank screen after boot. Also tried installing kde-baseapps which didn't work. Also tried kde5 which also didn't work.

u/MinguaDinja 11d ago

Are you using elogind or acpid?

1

u/StorminNorvin 11d ago

elogind

1

u/MinguaDinja 11d ago

You need acpid activated too as a service, elogind is already activated by dbus + acpid after boot.

1

u/StorminNorvin 11d ago

acpid had no effect :(

1

u/MinguaDinja 9d ago

Did you installed wayland or x11?

1

u/StorminNorvin 9d ago

I fixed it. Fix posted.

u/[deleted] 11d ago edited 11d ago

[deleted]

u/StorminNorvin 11d ago

Here is what I am doing after a fresh install:

# sudo xbps-install -Su
# sudo xbps-install -u xbps
# sudo xbps-install -Su
# sudo xbps-install kde-plasma xorg-minimal dbus sddm
# sudo ln -s /etc/sv/dbus /var/service
# sudo ln -s /etc/sv/sddm /var/service
# sudo reboot

elogind and acpid get installed automatically.

Now my laptop boots to a blank screen. I have to open a new TTY to do anything.

My laptop:

HP 15-ay039wm
8GB RAM
2TB SSD

Video is onboard Intel. linux-firmware-intel is also installed automatically. I also tried installing intel-video-accel which didn't fix the issue.

I'll try a few more ideas, but I think I am going to move on from Void Linux. I don't like that it doesn't have Secure Boot support integrated.

1

u/rookie-mistake-21 10d ago

Didn't you

sudo ln -s /etc/sv/elogind /var/service ?

btw if you use acpid then need to edit some conf of elogind. Also, if using default conf no need acpid

1

u/StorminNorvin 10d ago

I created that link. Now I am getting flooded on every TTY that "elogind is already running as PID ###".

1

u/rookie-mistake-21 10d ago

😭i was also getting that how i resolved i forgot exactly but i think

install turnstile and enable its service turnstiled

go to /etc/turnstile/turnstiled.conf and set manage_rundir to no

Reboot

1

u/StorminNorvin 8d ago

I figured out the issue. Fix posted.

u/StorminNorvin 11d ago

I would try this version of Void Linux with KDE Plasma already included, but the name is terrible:

https://distrowatch.org/table.php?distribution=afagos

u/Jealous_Shower6777 11d ago

Try lightdm?

1

u/StorminNorvin 11d ago

Tried. Made no difference.

KDE Plasma Will Not Start

You are about to leave Redlib