https://bugs.kde.org/show_bug.cgi?id=494231
Bug ID: 494231
Summary: When init is not systemd, krdpserver fails to start /
autostart / show status in kcm_krdpserver or kcm_kded.
Classification: Plasma
Product: KRdp
Version: 6.1.5
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: stev...@runbox.com
CC: ahiems...@heimr.nl
Target Milestone: ---
SUMMARY
On systems without systemd[user-units], krdpserver is not autostarted at login
or by the toggle in kcm_krdpserver.
KDE/Plasma already has a service manager, since when is it policy to break
portability by hardcoding systemd dependencies in new applications?
STEPS TO REPRODUCE
1. Run something other than systemd as init (sysvinit, openrc, runit, s6,
dinit, BSD rc.d, etc. etc.)
2. Toggle "Enable RDP server" on
3. Toggle "Autostart on login" on
OBSERVED RESULT
krdpserver process is not launched, "Enable RDP server" toggle reverts to off
upon reopening kcm_krdpserver.
krdpserver is not autostarted at login, despite "Autostart on login" being
enabled.
No discoverable error message is generated, STDERR prints "org.kde.krdp.kcm:
Toggling KRDP Server to true over QDBus" and nothing more.
Manually starting krdpserver works, "'Remote control" notification and systray
appear, but status is not reflected in kcm_krdpserver (toggle remains off).
EXPECTED RESULT
krdpserver starts when toggled on, autostarts at login when configured to do
so, and cleanly terminates with plasma session (as other plasma "background
services" do), regardless of init system in use.
SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.15
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.6.54-gentoo-dist (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
