Hi fedi, I am trying to install Void Linux in a virtual machine (as a stepping stone to considering running it as my main distro).

I managed to set up the base system and installed the
plasma-desktop and sddm packages, but I cannot actually get Plasma to launch. When I run startplasma-wayland from the tty, I get the following 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?
Note: I manually transcribed the error message from the VM screen, so I might have made a typo.

The same error results whether I am running a user or root terminal.

The [documentation says](docs.voidlinux.org/config/graphical-session/kde.html) that Plasma requires both the
dbus and sddm services, so I went back to the documentation on enabling services to enable both of them. They provide two methods of enabling services:# ln -s /etc/sv/dbus /var/service/and# ln -s /etc/sv/dbus /etc/runit/runsvdir/default/I tried both of these methods in separate copies of my VM, and then verified using sv status dbus and sv status sddm that the services were running. It made no difference: attempting to start plasma gives the same error. I tried using sv to restart both services and it made no difference.

Search engines did not yield anything helpful: all the results were
a) Discussions about Arch using SystemD, or
b) Folks asking for help starting Plasma 5 with x11.

Also, most folks asking for help on search engines could already start Plasma manually, but couldn't get it to start automatically on boot. I am not able to launch Plasma
at all.

I did find someone with the same question as me from almost a year ago, but no solution.
https://voidforums.com/viewtopic.php?t=764

So what can I do to get Plasma working on Void?

EDIT: SOLVED by
@alsorew ! I needed to install the xorg package despite wanting to use Wayland.

#VoidLinux #TechHelp @VoidLinux

Services and Daemons - runit - The Void Linux Handbook

@2something @VoidLinux that reads like dbus is running, but an indirect service isn't installed/running

a quick search says that the locale1 service is systemd-localed "systemd-localed.service(8) is a system service that can be used to control the system locale and keyboard mapping from user programs. This page describes the D-Bus interface."

TIL

so i guess either install/enable that, or convince plasma to not use it

@astraluma @VoidLinux But Void doesn't have systemd, hence my confusion.

@2something Sorry, I’m not an expert, so I can only be slightly more helpful than a yellow rubber duck.

Did you go through all the steps? This is what worked for me with Sway: https://mastodon.online/@alsorew/113629307036652701 Then, I installed KDE Plasma and Gamescope/Steam UI/whatever it’s called. I also have a Niri running in a VM. All my problems occurred when I missed a step or two. Void is a great toolbox, I love it, but you need to do everything yourself.

Andrew (@[email protected])

`sudo xbps-install -Su` `sudo xbps-install dbus-elogind elogind polkit mesa-dri sway foot xorg-fonts` `sudo ln -s /etc/sv/dbus /var/service/` `sudo ln -s /etc/sv/polkitd /var/service/` `sudo reboot` Login, `sway` The minimalist #Sway installation is done. #NotFullyLiveVoidPosting

Mastodon
@alsorew

@alsorew

I tried installing all the packages you mention except mesa-dri, foot, and sway, then linking polkitd. It doesn't make a difference.

Attempting to install mesa-dri gives an error, claiming it cannot download the dependency
libllvm21-21.1.7_1, "no child processes."

EDIT: Installing Sway and Foot, then launching
sway does work. Now let's see if I can install or launch Plasma from Sway....

EDIT 2: I've never used Sway before and I can't figure out how to open the terminal. All the online tutorials start with "here's how you write config files to customize keymappings" and not "here's the button you press to open the terminal so you can
find the config files."​
@2something The terminal (foot) should be Super+T, if I recall correctly.
@alsorew Nope, doesn't work for me. Nothing happens when I press super+T (or alt+T, or ctrl+T, or any combination I tried).

(This is not the first time I've tried to learn how to use Sway, and I've always gotten stuck on this step).
@2something Super+Enter?
@alsorew A ha! That works!
@alsorew Though I still can't get Plasma running now that I have foot. The error messages are the same as before.

@2something Okay, so if Sway works, I assume Wayland and the drivers are fine, too. Is it an Elogind problem? Try messing with this: https://docs.voidlinux.org/config/session-management.html

I’m going to make a VM for a test.

Session and Seat Management - The Void Linux Handbook

@2something Have you installed the `xorg` package? It was giving me the same error without it.

@2something Quick summary:
· `void-install` https://docs.voidlinux.org/installation/live-images/guide.html Nothing fancy: a US keyboard, locale, and packages from ISO.
· Update.
· Install `kde-plasma`. It pulls everything you need, except the terminal, so pick one or `kde-baseapps` (I assume it has Konsole).
· Install `xorg` (maybe `xorg-minimal` will work).
· Enable `dbus` and `sddm` (not sure if you need `polkitd`).
· Reboot.

I think that’s it. If you need it, I can redo everything more carefully with a more detailed description.

Installation Guide - The Void Linux Handbook

@alsorew I can't install the xorg package, since it depends on llvm21, which xbps says it can't download

ERROR [trans] failed to download libllvm21-21.1.7_1 package from https://mirrors.summithq.com/voidlinux/current : no child processesI can install other packages. Maybe I need to figure out how to switch mirrors.

mirrors

@2something How peculiar. But that means that’s the problem, 99% guaranteed! :)

Yeah, try using a different mirror.

Edit: I removed the second thing because it’s most likely irrelevant and just confusing. Also, it’s not a great long-term solution anyway.