Page MenuHome GnuPG

KGpg Fails to Autostart on Fedora 22 with KDE Despite 'Start KGpg automatically at login' Being Selected
Closed, ResolvedPublic


Event Timeline

The Problem: KGpg fails to automatically start at login on Fedora 22 with KDE.

I have KGpg configured with: Start KGpg automatically at login, selected.

This option is located at:

Configure KGpg, Misc, under the Global Settings tab.

I am running: gpg2 --version = gpg (GnuPG) 2.1.5 + libgcrypt 1.6.3

Following boot, and login, I have verified, using top, that KGpg is not running.

Furthermore, there is no KGpg launch/configuration/encryption icon available in
the System Tray, under Status & Notifications.

If I want to use KGpg, I must manually start KGpg. Following this manual
start, KGpg does indeed begin running, and is assigned a PID, then the
KGpg icon does appear in the Status & Notifications section of the System Tray.

Once manually launched, KGpg does work correctly.

Importantly, note that KGpg does autostart correctly, with a properly functioning
KGpg icon immediately available after login on both of my Gentoo Hardened and
Debian 8 rigs. Each of those operating systems run GnuPG 2.0.6, and both use
KDE with KGpg configured to automatically start at login.

I do not know whether this issue is being caused by 2.1.15, or something
KDE/Fedora did with KDE/Plasma5 in their release of Fed 22.

Any insights are appreciated.

Thanks for the report. We're not upsteam for KGpg and neither I nor Werner use
Fedora, which makes this issue difficult to debug. Can you please file a bug
report in Fedora's tracker? Thanks.

Also: feel free to add the link to this issue and if it does turn out to be a
problem with GnuPG add any information here. Thanks!

Hi Neal,

I understand your position on this issue.

As an interim heads up, I have documented this issue in the Fedora Forum. As my
post is only a few hours old, I'll keep an eye on it, and will be sure to let
you know if anything interesting shakes out.

I don't know what you mean by "documented the issue". The best thing to do is
to report the bug in the KGpg or Fedora bug tracker.

werner changed Version from 2.1.15 to 2.1.5.Jul 21 2015, 3:18 PM

Hi Neal,

I have spent several days debugging this AutoStart failure within the Fedora
Forum. However, none of that effort has yielded any useful information.

Therefore, I have filed a bug report on Fedora's bug tracker covering this
topic, available here:

I will let you know the outcome.

werner set External Link to 23 2015, 11:13 AM

Hi Neal,

Some positive progress to report. A workaround to brute force KGpg to AutoStart
on Fed 22 has been identified in the Fedora Forum where I've been working this

I have already appended this information to the official bug report in the hope
it helps the devs identify the underlying root cause.

I copy the workaround here so other users of this site and Fed 22 have a process
they can try if desired.

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

  1. Ensure ~/.config/autostart is empty. My autostart directory contained one

file , so I did:

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

  1. Copy the default startfile to the local user's autostart folder to override


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

  1. 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

  1. Save, Close, Logout
  1. 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.

Hi Neal,

A minor heads up.

I have appended the following to KGpg Failure to AutoStart bug report in the
hope it allows the devs to think about the nature of this problem's root cause
from a broader perspective:

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.

Kgpg is unmaintained upstream (meaning KDE) Afaik it does not work with gnupg 2.1

We (talking as a kdepim developer here) are currently in the process of removing
libkgpg dependencies in the hope to remove Kgpg altogether. You should use
Kleopatra and nag the Kleopatra developers (me) about features of KGpgp you will
miss in Kleopatra.

This bug has nothing to do with Gpg and should be filed on against
kgpg (but as I said it's unmaintained so you probably should not bother)

Based on aheinecke's comments I'm closing this.

neal claimed this task.
neal removed a project: Stalled.

I laughed when I first read aheinecke's comments, at least right up until the
moment the gravity of the 'unmaintained upstream' hit me!

The Bug I filed on 22 July at:

has gone exactly nowhere, in a hurry, despite being assigned to Ngo Than.

In any event, another Fedora Forum user and I tracked down the root cause ourselves.

I can confirm this KGpg failure to autostart is *NOT* in any way related to GnuPG.

I have already documented how to cause, and how to avoid, this KGpg autostart
failure in this thread:

Hint: If you are interested, read page 2 of ^that thread first, for a summary,
and a reproducible testing procedure.

aheinecke: Kleopatra was, and is, a 'thing' of beauty! ;-3

On 6 November, there was finally some movement on the 22 July Bug I filed at:

Rex Dieter provided the underlying explanation of the KGpg autostart failure on
Fedora 22 (or newer) systems:

He stated:

"Simple reason is that plasma5 doesn't support kde4 apps' use of

Note: Rex is also developing/testing a patch to address this plasma5
shortcoming for Fed 22 systems.

Importantly, and as I had suspected and alluded to, this plasma5 lack of support
explains why the KGpp failure to autostart occured *only* on my Fed 22 systems,
and did not impact any of the other KDE operating systems I use.

I have upgraded all my Fed 22 systems to Fed 23, where the KGpg autostart
currently continues to persist. I have documented the workaround in the Bug
report linked above for anyone impacted. This workaround also works in Fed 23.

Hopefully, this issue will be fully resolved in the next Fedora-approved release
of KGpg.

For the record Rolf Eike Beer still maintains KGpg (I was not aware of this when
i wrote T2048 (aheinecke on Aug 28 2015, 10:54 PM / Roundup))
And he is planning to port it to Qt5.

Please leave this issue closed here. This bug either belongs in the Fedora
Bugtracker or in KDE's bugtracker.