Scripts configured to run at startup and logoff are to being executed at all. The last time my backup script ran during logoff on my machine was 29 Dec 2017 - can't confirm when startup script stopped working as i have run it manually a couple of times. opensuse:tumbleweed:20180110 Qt: 5.10.0 KDE Frameworks: 5.41.0 - KDE Plasma: 5.11.5 - kwin 5.11.5 kmail2 5.7.0 - akonadiserver 5.7.0 - Kernel: 4.14.12-1-default
Updated to redirect bug to Plasma/kcm_kded - hopefully in the correct place
(In reply to BingMyBong from comment #1) > Updated to redirect bug to Plasma/kcm_kded - hopefully in the correct place Tracker didn't like that change, had to make it plasmashell/general
Please confirm it's not your script by adding: #!/bin/sh echo foo > /tmp/myScriptHasRan make sure this script is readable and executable by your user Also please check ~/.xsession-errors OR ~/.local/share/sddm/xorg-sessino.log for any output. Autostart scripts should print a line "Starting autostart script " << fullPath;
(In reply to David Edmundson from comment #3) > Please confirm it's not your script by adding: > > #!/bin/sh > echo foo > /tmp/myScriptHasRan These are the first 3 lines of the login script echo "working" > SIGNATURE-WORKING a=$(cat /etc/os-release | grep "CPE_NAME" | cut -b 18-45) echo $a >RELEASE_LEVELS It works fine when run from the cli but i do get these 3 errors displayed libGL error: unable to load driver: nouveau_dri.so libGL error: driver pointer missing libGL error: failed to load driver: nouveau > > make sure this script is readable and executable by your user -rwxr--r-- 1 is users 569 Jan 18 12:10 signature.sh > > Also please check ~/.xsession-errors OR ~/.local/share/sddm/xorg-sessino.log > for any output. i'm using kdm > Autostart scripts should print a line > > "Starting autostart script " << fullPath; These lines are in ~/.xsession-errors although systemsettings5 is configured to use "/home/is/signature.sh" ksmserver: Starting autostart script "/home/is/.config/autostart-scripts/signature.sh" ksmserver: Starting notification thread I added the same echo to a file with my logout script to make sure that worked manually too. These script files had been working for over a year quite happily.
Created attachment 109967 [details] xsession-errors after login a copy of the xsession-errors file just after login and then run cli
I changed to sddm and the scripts still do not run - see attached log for sddm
Created attachment 109999 [details] org-session.log for sddm session Log of sddm login session shows "signature.sh" script is accessed but it does not run and no error logged
BingMyBong, do you have "#!/bin/sh" at the start of your script? My startup script also stopped working last month, and after adding "#!/bin/sh" it started running during startup again. Though I wonder why that wasn't necessary before.
(In reply to kafei from comment #8) > BingMyBong, do you have "#!/bin/sh" at the start of your script? My startup > script also stopped working last month, and after adding "#!/bin/sh" it > started running during startup again. > > Though I wonder why that wasn't necessary before. No, I didn't. I added to both my startup and logout script but only the logout script worked. Thanks.
(In reply to David Edmundson from comment #3) > Please confirm it's not your script by adding: > > #!/bin/sh > echo foo > /tmp/myScriptHasRan > > make sure this script is readable and executable by your user > > > > Also please check ~/.xsession-errors OR ~/.local/share/sddm/xorg-sessino.log > for any output. > > Autostart scripts should print a line > > "Starting autostart script " << fullPath; I've now added "#!/bin/sh" to both startup and logout scripts but it only makes the logout script work. I originally only tried it with the startup script and that didn;t work so i mistakenly assumed it wouldn't work with the logout script. I'll add the latest .xsession-errors file
Created attachment 110112 [details] xsession errors for kdm login autostart issue
oh balls... I had a blank line in the startup script before the "#!/bin/sh" and that stopped it working. It works fine now. I'll close this bug