On Fri, May 7, 2021 at 11:15 AM Barry Scott <barry@barrys-emacs.org> wrote:
I have been using a login task for a number of years with KDE.

After the upgrade to F34 KDE is no longer running my login script.

I added some logging to the script to leave evidence that it has run
and no logs are recorded.

I tried deleting the existing entry in
System Settings/Startup and Shutdown/autostart
then I added the script back in.

But that did not work.

Is there something special I need to do to make this work?
Is there a log somewhere that I can check for errors?

Barry
_______________________________________________
kde mailing list -- kde@lists.fedoraproject.org
To unsubscribe send an email to kde-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

I've been able to overcome this by placing my script in $HOME/.config/plasma-workspace/env instead.
The Help Centre section for Autostart mentions this directory as one of the paths being searched:
The program scans $HOME/.config/autostart/, $HOME/.config/plasma-workspace/env and $HOME/.config/plasma-workspace/shutdown folders to check what programs and scripts are already there and displays them. It allows you to manage them easily.
 
Scripts set to run at Pre-Plasma Startup are copied or symlinked in $HOME/.config/plasma-workspace/env and are sourced during Plasma startup (the startkde script will look for scripts here).

Only scripts with the .sh extension can be read by Plasma for Before session startup and Shutdown modes.