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

On 21 May 2021, at 20:00, Barry Scott <barry(a)barrys-emacs.org&gt; wrote: > On 7 May 2021, at 17:56, Robert-André Mauchin <zebob.m(a)gmail.com <mailto:zebob.m@gmail.com>> wrote: > > On 5/7/21 10:15 AM, Barry Scott 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 > > Mine don't work too. I've elected to make a user service file in: > > ~/.config/systemd/user/ > > For example: > > # ssh-add.service > [Unit] > Description=ssh-add service > Requires=ssh-agent.service > After=ssh-agent.service > > [Service] > ExecStart=ssh-add -q %h/.ssh/id_rsa > > [Install] > WantedBy=xdg-desktop-autostart.target Robert, I like this as it uses the new --user systemd unit to do the init. I know that this is the future of better DE startup. The env suggestion does not work as ssh-aganet is not running when then env is setup. But I have one problem and wonder is you found a fix. I get prompted for the password for the wallet. I tried adding: After=dbus-:1.2-org.kde.kwalletd5@1.service <mailto:1.2-org.kde.kwalletd5@1.service> To make sure the wallet was up, but it looks like I need to be After: some target that says that the required services are not just running but have beenc onfigured. The other observation is that this works for plama X11. But it does not work for plasma wayland as there is not ssh-agent running. I have not tried to figure out why yet.

On Fri, May 7, 2021 at 11:15 AM Barry Scott <barry(a)barrys-emacs.org <mailto: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(a)lists.fedoraproject.org <mailto:kde@lists.fedoraproject.org> To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org <mailto:kde-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ <https://docs.fedoraproject.org/en-US/project/code-of-conduct/> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines <https://fedoraproject.org/wiki/Mailing_list_guidelines> List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org <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 <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. _______________________________________________ kde mailing list -- kde(a)lists.fedoraproject.org To unsubscribe send an email to kde-leave(a)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

On Sat, 2021-05-15 at 10:36 -0400, Pizza Dude wrote: > kwriteconfig5 --file startkderc --group General --key systemdBoot false > What does this mean?