We have too many autostart directories... freedesktop.org clearly states: "By placing an application's .desktop file in one of the autostart directories the application will be automatically launched during startup of the user's desktop environment after the user has logged in. [...] The autostart directories are: ~/.config/autostart/ (personal autostart directory) /etc/xdg/autostart/ (system wide autostart directory)" In practice, however, at least six folders are being checked for .desktop files, wich creates, let's say, a bit of confusion: ~/.kde/Autostart/ ~/.kde/share/autostart/ ~/.config/autostart/ ~/.local/share/autostart/ /etc/xdg/autostart/ /usr/share/autostart/ Reproducible: Always
Please see the related Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=879946
I don't see any incompliance here. Everything required by FDO is correctly supported by KDE. Those extra locations are for KDE specific needs, and FDO doesn't say implementations are *forbidden* to add their private locations to meet their specific needs. Also, what is really expected under "~/.kde/Autostart/" are executable scripts, although .dekstop file is also supported.
Ok... Why is there "/usr/share/autostart/" when we already have "/etc/xdg/autostart/" ? PS: KDE-only apps could make use of the "OnlyShowIn=KDE" trick.
true, /usr/share/autostart and ~/.kde/share/autostart are kde-specific , but removing them (or support for them) now is too late, and risks breaking existing users and systems. As I mentioned in the downstream report, i have doubts there's anything actionable to be done here.
ok
Hello. I am using the Plasma KDE 5.13.3 compilation and it seems to not be considering the directory: /etc/xdg/autostart Found this because of an issue with geoclue 2.4.10 which denied me the service to use it with Redshift and made it work by making a symbolic link of the geoclue demo agent XDG autostart file geoclue-demo-agent.desktop to ~/.config/autostart: ln -s /etc/xdg/autostart/geoclue-demo-agent.desktop ~/.config/autostart Also consider that geoclue relies on XDG's compliance.
I'm going to close this bug fyi. As for the latest comment, I can assure you that plasma5 does comply with XDG standards, autostart in particular, in general. Many plasma services, including baloo, powerdevil, polkit-kde-authentication-agent, etc... rely on that successfully. If you believe you've found a new bug, I strongly suggest you file a new issue. Thanks.