Bug 1245732

Update:  A workaround to brute forcing KGpg to AutoStart has been identified in the Fedora Forum within the same thread I originally linked.

I hope the workaround helps you find the actual root cause of this failure.

Quoting in relevant part:

As a workaround to KGpg's failure to AutoStart, this brute force method works on my Fed 22/KDE system:

1. Manually start kgpg from Konsole:

$ kgpg

2. Ensure ~/.config/autostart is empty. My autostart directory contained one file , so I did:

mv /home/<username>/.config/autostart/kgpg.desktop /home/<username>

3. Copy the default startfile to the local user's autostart folder to override defaults:

cp /usr/share/autostart/kgpg.desktop /home/<username>/.config/autostart/

4. Edit the ".config/autostart/kgpg.desktop" file by setting autostart to "true" (from it's default value of 'false")

X-KDE-autostart-condition=kgpgrc:User Interface:AutoStart:true

5. Save, Close, Logout

6. Following Login, note that KGpg is 'autostarted'. This means the KGpg icon is available in the System Tray, under Status & Notifications, and KGpg has been assigned a PID, and is running. Clicking on the KGpg icon shows that all KGpg functions work correctly.

This brute force method is also known to survive subsequent logouts - logins, and reboots.

Additionally, note re:  the failure of KGpg to AutoStart: 

All of the testing I've described in this bug report, and on the Fedora Forum link, was performed using a native Fed 22 system installed on a HDD.  On this HDD-based system, I had previously run Fed 21, and used fedup to arrive at Fed 22.  

However, I also run Fed 22 as a Guest OS in both VBox and KVM.  Installation of both of these virtual Guests was accomplished using the Fed 22 KDE Spin *.iso.

IIRC, when Fed 22 is first cleanly installed from the *.iso, the gpg2 version installed is:  2.1.14.  After the first:  dnf upgrade is performed, gpg2 version 2.1.15 gets pulled in.

Despite these differences, in all three of my Fed 22 installations, KGpg fails to AutoStart, despite being enabled.

The following set of facts is also included within the above referenced Fedora forum thread discussing this bug, which is linked above.

However, to make it abundantly clear why I believe this KGpg Autostart failure is unique to Fedora 22, please keep these facts in mind when thinking about the root cause of this failure:

1. In all other operating systems I use, I have the full blown KDE environment installed, just as I do with Fed 22.

2. In all other operating systems I use, I have KGpg set to autostart, just as I do with Fed 22.

3. In all other operating systems I use, I have KDE set to 'Start with an empty session,' just as I do with Fed 22.

4. In all other operating systems I use, KGpg autostarts correctly.

5. Fed 22 is the sole exception, and the only OS I use where KGpg fails to autostart, despite being enabled in the KGpg configuration GUI, and, of course, the underlying configuration file:

/home/<username>/.kde/share/config/kgpgrc

has these values, correctly, set:

[User Interface]
AutoStart=true

Those reasons are why I continue to believe this bug is solely related to code changes made in Fedora 22's version of KDE and/or Plasma 5.

Simple reason is that plasma5 doesn't support kde4 apps' use of 
X-KDE-Autostart-condition

I've got a hack to make it work though, coming soon

kgpg-15.08.2-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-e8d90a10ae

kgpg-15.08.2-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-e8d90a10ae

Rex,

A few thoughts:

1.  Thank you for addressing this issue.

2.  Your explanation that plasma5 doesn't support kde4 apps' use of 
X-KDE-Autostart-condition makes perfect sense.

3.  As a result of learning about the lack of plasma5 support, now I understand why my Fed 22 system was the only OS I used where KGpg failed to autostart.

4.  I wish I had understood this concept back in July, but better late than never.

5.  I'm glad you developed the patch.

6.  I'm sure it is easy enough for you to test on your end.  However, given your patch submission on 6 Nov, it is 3 days too late for testing on my end.

7.  All of my Fed 22 systems, both native and virtual, were upgraded to Fed 23 on 3 Nov.

8.  The brute force method I discussed above still works in Fed 23.  As you might expect, if you change:

X-KDE-autostart-condition=kgpgrc:User Interface:AutoStart:true

from true to false; the KGpg failure to autostart returns after the the next login, reboot, etc.

9.  kgpg-15.08.1-1.fc23.x86_64 is the version of KGpg which is currently installed on a fully updated Fed 23 KDE system.

10.  Thanks again for your effort, Rex.

6 and 7: this affects f23 too (or any system using plasma5)

Since this bug was filed against f23, I didn't reference any f23 updates here, but I will do so now.

kgpg-15.08.2-1.fc23 : 
https://bodhi.fedoraproject.org/updates/FEDORA-2015-7e26cafdf3

kgpg-15.08.2-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update kgpg'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-e8d90a10ae

kgpg-15.08.3-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-7e26cafdf3

kgpg-15.08.3-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-e8d90a10ae

kgpg-15.08.3-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update kgpg'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-e8d90a10ae

kgpg-15.08.3-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update kgpg'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-7e26cafdf3

kgpg-15.08.3-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-7e26cafdf3

kgpg-15.08.3-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-e8d90a10ae

kgpg-15.08.3-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update kgpg'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-e8d90a10ae

kgpg-15.08.3-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update kgpg'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-7e26cafdf3

kgpg-15.08.3-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.

kgpg-15.08.3-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.