Bug 494231

Summary:	When init is not systemd, krdpserver fails to start / autostart / show status in kcm_krdpserver or kcm_kded.
Product:	[Plasma] KRdp	Reporter:	Steve Vialle <steve_v>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	REPORTED ---
Severity:	normal	CC:	ahiemstra
Priority:	NOR
Version:	6.1.5
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Steve Vialle 2024-10-07 07:29:15 UTC

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