Bug 484207

Summary:	Autostart KCM doesn't work with desktop files containing spaces
Product:	[Applications] systemsettings	Reporter:	gudvinr+kde
Component:	kcm_autostart	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	kde, nate, nicolas.fella, sourcework
Priority:	NOR
Version First Reported In:	6.0.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description gudvinr+kde 2024-03-22 05:52:19 UTC

SUMMARY

When you have .desktop files with spaces in the name added to .config/autostart/, KCM shows "Not autostarted yet".
But in fact, startup script for systemd was generated and running.

I think that KCM doesn't correctly handle systemd escape rules for whitespaces.

STEPS TO REPRODUCE
1. Create .desktop file containing space in .config/autostart/
2. Restart system

OBSERVED RESULT
Service is started. KCM doesn't see it.

EXPECTED RESULT
KCM showing status of the daemon.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.6.22-1-lts (64-bit)
Graphics Platform: X11

Comment 1 kderocks38 2025-04-14 15:12:45 UTC

Same on 6.2.5 on fedora 41.

If you add a script with space in it, then it does not work. I don't mind it that it has to be this way, but could there be an info message message regarding this when you click on "add connexion script" in from the autostart gui?

Similar situation discussed here 
https://discuss.kde.org/t/application-in-autostart-not-started-yet-even-though-i-restarted-plenty-of-times-already/13739/2