Summary: | kde-plasma/plasma-workspace fails to start with wayland on openrc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | gentoo |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
gentoo
2016-02-17 16:34:49 UTC
plasma requires the logind interface, which usually means systemd. If you're keen, you could try sys-auth/elogind from the KDE overlay. Created attachment 425730 [details]
emerge --info
I'll read more about systemd and elogind. If Wayland expects systemd, should the setting of the wayland USE flag then not also pull in systemd somehow? The logind interface is normally implemented by systemd, but in theory could be implemented by anything. Projects such as elogind popped up to allow use of this feature instead of switching to systemd. In theory, simply installing elogind should be enough as it will be called at runtime via dbus. I've now changed the system to use systemd instead of OpenRC. So far, so good. However, the error message is exactly the same as before. When I log in to KDE using lightdm and the "Wayland" plasma session, the screen goes black for an instant, then the login prompt is back. From a TTY I can read the .xsession-errors file, and it contains the same message as before about not being able to start D-Bus. When I type "qdbus" at the command line, I get a listing that includes two items, :1.0 org.freedesktop.systemd1 :1.2 org.freedesktop.DBus This error doesn't seem to be caused by configuration options in my user's .kde4 directory because even when I rename that, it's the same error. I've switched to systemd and changed a few other things, so marking this as Resolved because I won't be able to reproduce the bug now. |