SUMMARY I changed my $XDG_CONFIG_HOME to another path, and placed desktop file in $XDG_CONFIG_HOME/autostart. The program won't autostart in KDE. However if I manually create ~/.config/autostart and put desktop file in it, the program can autostart with KDE. STEPS TO REPRODUCE 1. Change $XDG_CONFIG_HOME in your profile and placed desktop file in $XDG_CONFIG_HOME/autostart 2. Reboot 3. OBSERVED RESULT The program won't autostart in KDE. EXPECTED RESULT The program autostarts in KDE. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Gnome can recognize $XDG_CONFIG_HOME/autostart after $XDG_CONFIG_HOME is changed, and autostart program with no problem. According to XDG Autostart specification, DE should recognize the $XDG_CONFIG_HOME/autostart path: https://wiki.archlinux.org/title/XDG_Autostart
Plasma uses QStandardPaths::GenericConfigLocation for all relevant operations which reads XDG_CONFIG_HOME. Does it work after you ran "kwriteconfig5 --file startkderc --group General --key systemdBoot false" ? If yes that looks like a problem with the xdg autostart generator
>XDG_CONFIG_HOME Please confirm how you changed this?
(In reply to Nicolas Fella from comment #1) > Plasma uses QStandardPaths::GenericConfigLocation for all relevant > operations which reads XDG_CONFIG_HOME. > > Does it work after you ran "kwriteconfig5 --file startkderc --group General > --key systemdBoot false" ? If yes that looks like a problem with the xdg > autostart generator Yes it works after running that. I'll file a bug to systemd.
(In reply to David Edmundson from comment #2) > >XDG_CONFIG_HOME > > Please confirm how you changed this? I put export XDG_CONFIG_HOME=$HOME/.local/config in /etc/profile.d/profile.sh
I think the only way to properly set XDG_CONFIG_HOME is through /etc/security/pam_env.conf
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!