https://bugs.kde.org/show_bug.cgi?id=404335
Bug ID: 404335
Summary: Don't rely on dbus-run-session or dbus-launch for
starting plasma-wayland session
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Keywords: wayland
Severity: normal
Priority: NOR
Component: generic-wayland
Assignee: plasma-b...@kde.org
Reporter: itgvk...@grr.la
Target Milestone: 1.0
SUMMARY
Currently plasma-wayland session is launched through dbus-run-session like:
dbus-run-session /usr/bin/startplasmacompositor
The problem with this is that the dbus-broker
(https://github.com/bus1/dbus-broker) which is a new, modern, direct
replacement for dbus implementation doesn't have equivalent of dbus-run-session
command (https://github.com/bus1/dbus-broker/issues/145). Plasma x11 session
isn't affected as it doesn't use dbus-run-session command to start itself.
When dbus-broker is used on system then starting plasma-wayland through
dbus-run-session will start the old dbus daemon which will be disconnected from
the former thus connection to dbus services won't work.
dbus-broker is already available in various distro repositiories (Arch Linux,
Fedora, openSUSE) and there is actual plan to make dbus-broker the default dbus
implementation in Fedora
(https://fedoraproject.org/wiki/Changes/DbusBrokerAsTheDefaultDbusImplementation)
- currently postponed to F30. Other distros will follow sooner or later.
--
You are receiving this mail because:
You are watching all bug changes.
