Discussion:
[kleopatra] [Bug 401933] Cannot select signing key
Matthieu Gras
2018-12-10 16:33:23 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=401933

--- Comment #10 from Matthieu Gras <***@student.ethz.ch> ---
Just checked phabricator, the fix I was going to propose is already in
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
Andre Heinecke
2018-12-10 14:19:13 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=401933

Andre Heinecke <***@intevation.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal

--- Comment #7 from Andre Heinecke <***@intevation.de> ---
Honestly,.. I have absolutely no idea how this is possible or what the reason
for this could be. :-/ There is nothing special with your key, maybe except for
the "Authentication" capability on the primary key but that should be no issue.

My next step here would be to try to reproduce your setup in a virtual machine.

In the meantime you could install GPA which has a "clipboard" which is
comparable to Kleopatra's.

As a last question: If you generate a test key in Kleopatra with the defaults
does it work then?
--
You are receiving this mail because:
You are on the CC list for the bug.
Matthieu Gras
2018-12-10 14:28:05 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=401933

--- Comment #8 from Matthieu Gras <***@student.ethz.ch> ---
No even with the default settings I get the exact same behavior. The behavior
also isn't really deterministic. If I do
pkill kleopatra && kleopatra
sometimes everything is fine, sometimes nothing works and sometimes only
encryption or only signing work.

The problem is that signing E-Mails in Kmail also doesn't work anymore.
Thank you, maybe I'll have a look at the source code if it's not too
convoluted.
--
You are receiving this mail because:
You are on the CC list for the bug.
Andre Heinecke
2018-12-10 07:27:46 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=401933

Andre Heinecke <***@intevation.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO

--- Comment #1 from Andre Heinecke <***@intevation.de> ---
This should only happen if your key is disabled / exipred or revoked. Or if you
do not have a suitable key:

Do you have an ultimately trusted private OpenPGP key?

If you select "My Certificates" in the keylist, what does it show?

Can you please attach a screenshot of that if it shows your key?


Thanks!
Andre
--
You are receiving this mail because:
You are on the CC list for the bug.
Matthieu Gras
2018-12-10 18:02:18 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=401933

--- Comment #14 from Matthieu Gras <***@student.ethz.ch> ---
(In reply to Andre Heinecke from comment #11)
Awesome, thanks for looking into this !
So you have a version that contained my Friday bug (sorry for that)
db3fd6ea8c6619da75b9903a90fffc0f9330cf12
But not my Monday fix 98cf4b67ac005832a0ada734ba805e10e51a0319
That is a weird version! Does SUSE Leap just use random git master snapshots?
There was no tag or so in between. I've just checked (to be sure that the
fix was properly included in the applications 18.12 branch).
Anyway. Thanks for your efforts trying to help making Kleopatra better!
(btw. other contributions are always welcome ;-) )
Stock Leap uses the 5.12 LTS. I'm using the additional (semi-offical) KDE repo,
I think my KDE applications are at version 18.11.90.
--
You are receiving this mail because:
You are on the CC list for the bug.
Loading...