Summary: | Autostart script to unlock ssh keys doesn't seem to be launched when using systemd startup | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Kevin C <kevin> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alex, kevin, nate, ngompa13, plasma-bugs-null, rverschelde |
Priority: | NOR | ||
Version First Reported In: | 5.21.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/-/commit/93f9ef0304f300dc3952ac9a25cbd82996eec263 | Version Fixed In: | 5.22 |
Sentry Crash Report: |
Description
Kevin C
2021-03-15 13:52:50 UTC
x or wayland? X11 Are you using systemd startup? I'm using Systemd startup. I tested same configuration in a fresh Debian 10 instance with KDE Plasma : 5.14.5 KDE Framework : 5.54.0 Qt : 5.11.3 and it works. works too in Debian testing with KDE Plasma : 5.20.5 KDE Framework : 5.78.0 Qt : 5.15.2 Can confirm that running `ssh-add` via autostart does not work with systemd startup, and does work without it. You're using released packages, so this isn't Bug 427340. I also see this after an (early) upgrade to Fedora 34. The ~/.config/autostart-scripts/ssh-add.sh script I had which was previously working on Fedora 33 no longer executes at startup, despite showing in the list in Autostart in System Settings. However, adding a .desktop file in ~/.config/autostart to run a script doing the same thing does work: [Desktop Entry] Type=Application Name=ssh-startup Exec=/home/alex/bin/ssh-startup.sh StartupNotify=false Terminal=false This is using systemd startup (appears to be default in Fedora 34) on Wayland, with: Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Fixed by Henri Chain with https://invent.kde.org/plasma/plasma-workspace/-/commit/93f9ef0304f300dc3952ac9a25cbd82996eec263 in Plasma 5.22! |