Mark and Simon: thank you. Mark Hindley - 06.03.23, 17:22:12 CET: > On Mon, Mar 06, 2023 at 03:25:18PM +0000, Simon McVittie wrote: > > What I absolutely don't want is to make the change, and then 2 years > > later get hate mail from someone telling me that I've broken their > > system by making dbus-launch prevent /home from being unmounted and > > "why can't you just" add an option to use daemon(3). > > I think that is a very good point. > > KDE is the only area where I have heard of this causing problems and I > am not aware of any other reports that seem to have the same > underlying cause. …
The upstream issue¹ refers to GNOME applications in RHEL 7 being affected. RHEL 7 would have a KDE without Systemd startup I bet². [1] https://gitlab.freedesktop.org/dbus/dbus/-/issues/214 [2] https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ (however I am not entirely sure whether that kind of startup is activated by default nowadays) > I am not convinced there *is* a consensus for change and the risk of > changing the default for all users of legacy DBus activation seems > high. Fair enough. > Martin, I still think this is for KDE to address if it is important to > them. I don't think I would push to change the behaviour of DBus in > either Debian or Devuan at the moment. I added that information and suggestion to the KDE bug report: krunner starts applications with cwd "/" with init system other than systemd (openrc, runit, ...) https://bugs.kde.org/show_bug.cgi?id=432975#c16 Let's see whether KDE developers are open to make the required changes. Thanks, -- Martin