I encounter this issue in Fedora 34 Beta, but not in KDE Neon Unstable. Someone else has reported that this issue occurs on openSUSE Tumbleweed. I have been told that this is due to those distros shipping a newer version of systemd than Neon does. Looking through journalctl /usr/bin/plasmashell, there is this line: kf.kio.gui: Failed to register new cgroup: "app-autostart-4e12cde8171d4a88b8c761993c183409.scope" "org.freedesktop.DBus.Error.AccessDenied" "Failed to get file context on /home/alex/autostart.desktop." And here is a downstream report of this issue: https://pagure.io/fedora-kde/SIG/issue/50
On Tumbleweed (March 30 and up), I do NOT have this problem, only on the Fedora 34 beta.
Can you clarify what doesn't apply properly?
On Fedora 34 KDE beta, setting a program to launch on login through Autostart creates a `.desktop` file which is NOT run at login. So in fact the program does not autostart.
I don't think that particular line is relevant, we want the one from the generator. Can you include the whole log, or at least include your .desktop file
I'm not sure how much logging detail I should include, or how best to get that log, but I was scrolling through journalctl and saw this from systemd-xdg-autostart-generator: /etc/xdg/autostart/org.kde.dolphin.desktop:109: Unknown key name 'InitialPreference' in section 'Desktop Entry', ignoring. I will attach the .desktop file that line refers to.
Created attachment 137731 [details] Generated .desktop file
Setting back to REPORTED as I have provided the requested info. If there is anything else you need, please let me know.
What systemd version do you have? If it's 248 or earlier, then this is Bug 433299, which is fixed in systemd 249.
(In reply to Nate Graham from comment #8) > What systemd version do you have? If it's 248 or earlier, then this is Bug > 433299, which is fixed in systemd 249. I probably should have said this to begin with... It's systemd 248. Thanks.
Gotcha. So then this is Bug 433299, and it should be fixed with Systemd 249. *** This bug has been marked as a duplicate of bug 433299 ***