https://bugs.kde.org/show_bug.cgi?id=420975
Méven Car <meven....@enioka.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |NOT A BUG
Status|NEEDSINFO |RESOLVED
--- Comment #8 from Méven Car <meven....@enioka.com> ---
(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.
--
You are receiving this mail because:
You are watching all bug changes.
