Red Hat Bugzilla – Bug 1236356
gpg-agent not auto-starting, /etc/xdg/plasma-workspace/env/gpg-agent-startup.sh missing after update
Last modified: 2015-08-26 15:21:27 EDT
Description of problem: After recent updates, my gpg-agent is not auto-starting in KDE. It looks like the startup script is gone. ls: cannot access /etc/xdg/plasma-workspace/env/gpg-agent-startup.sh: No such file or directory dnf provides /etc/xdg/plasma-workspace/env/gpg-agent-startup.sh Last metadata expiration check performed 0:11:05 ago on Sun Jun 28 00:42:12 2015. kde-settings-plasma-22-7.fc22.noarch : Configuration files for plasma Repo : fedora rpm -q kde-settings-plasma-22-7 package kde-settings-plasma-22-7 is not installed rpm -q kde-settings-plasma kde-settings-plasma-22-11.fc22.noarch Version-Release number of selected component (if applicable): kde-settings-plasma-22-7.fc22.noarch.rpm has the script kde-settings-plasma-22-11.fc22.noarch.rpm does not How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hmm, It looks like this was intentional. Maybe I just need to figure out the whatever the proper way is of having that running. http://koji.fedoraproject.org/koji/buildinfo?buildID=646368 Tue Jun 16 2015 Rex Dieter <rdieter@fedoraproject.org> - 22-11 - env: set GDK_CORE_DEVICE_EVENTS=1 to workaround gtk3 scrolling issues (#1226465) - env: omit gpg-agent management, no longer needed (#1229918) I gave up searching too soon before hitting new bug. In case anyone has a recommendation, I was using the gpg-agent's --enable-ssh-support option with a YubiKey for it to just work in all my Konsole terminals when plugged in.
Yeah, the old script didn't work right anymore as gnupg2 changed behavior a bit (and gpg-agent autostart's itself now on demand), see aforementioned bug #1229918
marking NOTABUG