Bug 484207 - Autostart KCM doesn't work with desktop files containing spaces
Summary: Autostart KCM doesn't work with desktop files containing spaces
Status: REPORTED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_autostart (other bugs)
Version First Reported In: 6.0.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-22 05:52 UTC by gudvinr+kde
Modified: 2025-04-14 15:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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