| Summary: | The "System Settings" > "Startup and Shutdown" > "Autostart" > "Script File" does not get executed. | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | remyvrs <remyvrs> |
| Component: | kcm_autostart | Assignee: | Laurent Montel <montel> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | meven.car, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.18.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
remyvrs
2020-05-04 02:43:38 UTC
*** Bug 420976 has been marked as a duplicate of this bug. *** Works for me. Can you make sure the script file is marked as executable? Hi, yes, the file is executable first of all I do not have a fresh install, I have upgraded from 18.04 and this is a setup that I previously had and it worked. secondly, since it does not work automatically I am currently executing it manually, hoping that this would get fixed :) Thanks for the info. I don't reproduce. I tested also with the upcoming refactoring branch. The script I added was : cat ~/touch_desktop_file.sh : #!/bin/bash touch ~/Desktop/test And could see a test file on my desktop after reboot It may be a stupid question but, did you test your script manually ? What returns ? `ls -l ~/.config/autostart-scripts/` It should contain a copy of your script or a link to it. HI, actually it is not a stupid Q :) But yes, as stated, since it is not executed automatically I run the script manually until the issue will get fixed. So, yes, the script runs OK. I will get back with the other details.. I've tried your script and it worked (got auto executed during start). Turns out that the script must start with "#!/bin/bash" and my script didn't had that ... and all my other tries were without. This wasn't an issue before the upgrade from 18.04 to 20.04 . Anyway, I have my solution now, at least for my case and I leave up to you the resolution for this issue. Best Regards, Remus (In reply to remyvrs from comment #7) > I've tried your script and it worked (got auto executed during start). > Turns out that the script must start with "#!/bin/bash" and my script didn't > had that ... and all my other tries were without. I a feeling it could be this, it is the next classical issue after missing exec permission for script launches. > This wasn't an issue before the upgrade from 18.04 to 20.04 . I guess this changed due to the new startkde program introduced in 2018 that was responsible to speeding up the starting of plasma. http://blog.davidedmundson.co.uk/blog/plasma-startup/ Not having a script env header is bad practice, the kind of stuff that will prevent your script to run in cron for instance. > > Anyway, I have my solution now, at least for my case and I leave up to you > the resolution for this issue. > Since it was a misconfiguration, it is "Not a bug" IMO. Maybe the kcm could help prevent such cases though. |