343513 2015-01-29 12:16:45 +0000 custom startup scripts set in systemsettings5 not working 2015-08-29 12:21:09 +0000 1 1 2 Applications systemsettings kcm_autostart 5.2.0 Gentoo Packages Linux RESOLVED DUPLICATE 346862 NOR normal --- 0 mschiff montel AndyKluger bshah chrno-sphered cristian.mqa.dev erik herman.viaene jpwhiting kde kde merikes.lists samrog131 travneff 0 oldest_to_newest 1495547 0 mschiff 2015-01-29 12:16:45 +0000 In systemsettings (autostart) a user can add "Script file" and the can select via "Run On", what to do with it. Setting a Script to "Shutdown" or "Pre-KDE startup" works find, but "Startup" does NOT. For "Startup" a script will be symlinked to ~/.config/autostart/ and will NOT be run at startup. In fact on the next startup of systemssettings5 it will not even be displayed anymore under the "Script file" section. This is severly broken. Additional note: The item texts from the drop down menu "Run on" are very misleading. It should be made clear, that "Pre-KDE startup" will just set ENV variables and files mention here SHOULD CONTAIN ONLY ENV variable settings and a script set for this should NOT contain any commands like "exit 0" for example which will prevent plasma startup at all! Maybe better solution: Rename the columns from "Run on" to "Script action" - "Execute on startup" - "Extend environment before startup" - "Execute on shutdown" Reproducible: Always 1495579 1 montel 2015-01-29 12:47:36 +0000 "In fact on the next startup of systemssettings5 it will not even be displayed anymore under the "Script file" section. This is severly broken. " Yes I didn't understand this commit "1a7ed091d897e8f01076a4a26388b82c2c8f5836" from Jeremy Whiting it's totally illogic because we add script and we don't display it after that. I add jpwhiting@kde.org to this bug report 1495688 2 jpwhiting 2015-01-29 17:24:39 +0000 I added not showing custom scripts there because we don't run them anyway, so why show them. I guess we also need to make it not add them, since we aren't executing them either. Or make klauncher/kinit start custom scripts again. 1495690 3 montel 2015-01-29 17:26:47 +0000 It will more logical to not allow to create it if we can't execute it. But indeed it will better to fix klauncher. But until it it's better to disable create it no ? 1495692 4 jpwhiting 2015-01-29 17:28:17 +0000 I agree, I didn't realize it let you create it in the gui when I made that change. 1502135 5 AndyKluger 2015-02-25 17:28:23 +0000 I have been re-adding startup scripts every single time I log in, on multiple computers. It is incredibly frustrating to find out that for a month this bug has been known and yet no move has been made, either to make the function work, or to remove the false advertisement of functionality. Instead the user is left with a trap. Does anybody have a clean alternative for starting scripts automatically? 1502144 6 jpwhiting 2015-02-25 18:41:55 +0000 KInit does not launch any scripts, only entries with .desktop files as per the XDG spec. A workaround is to place scripts into ~/.config/plasma-workspace/env/ I'll remove adding scripts from the kcm since that's indeed a broken functionality. 1502186 7 AndyKluger 2015-02-25 22:13:42 +0000 Thanks Jeremy. I tried the workaround you suggested with two scripts, and it seems to run only one of them. Is there a space where these run attempts are logged? 1502189 8 jpwhiting 2015-02-25 22:40:00 +0000 Andy, Hey, I'm not sure where they are logged, likely .xsession-errors or journalctl . By the way I looked into this a bit more today and it seems that you can have the kcm put the script into ~/.config/plasma-workspace/env/ by changing them to "Pre-KDE start" in the ui. 1511563 9 chrno-sphered 2015-04-15 15:46:03 +0000 I'm having the opposite problem - shutdown scripts are not being executed. I have tried putting a script into ~/.config/plasma-workspace/shutdown (where a link to it was created by kcm) and it ignores it as well. What IS a working solution to running script at shutdown atm? I used to use the nm-dispatcher service to unmount any shares before my wlan connection goes down, but ever since I installed plasma and sddm, those are only ran at logout, not shutdown/restart. 1512103 10 samrog131 2015-04-18 07:08:40 +0000 Duplicate of the https://bugs.kde.org/show_bug.cgi?id=338242 ? 1516341 11 jpwhiting 2015-05-05 15:05:48 +0000 *** Bug 347206 has been marked as a duplicate of this bug. *** 1519488 12 thomas.luebking 2015-05-17 09:19:40 +0000 *** Bug 347206 has been marked as a duplicate of this bug. *** 1528662 13 cristian.mqa.dev 2015-06-27 16:51:49 +0000 *** Bug 349663 has been marked as a duplicate of this bug. *** 1538255 14 kde 2015-08-20 14:38:12 +0000 *** This bug has been marked as a duplicate of bug 346862 ***