Bug 186001 - kleopatra is unable to change passphrase of existing gpg certificate
Summary: kleopatra is unable to change passphrase of existing gpg certificate
Status: RESOLVED WORKSFORME
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Marc Mutz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-02 22:36 UTC by Heinz Wiesinger
Modified: 2013-05-08 08:09 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heinz Wiesinger 2009-03-02 22:36:55 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Compiled From Sources

When clicking on "Change Passphrase..." in kleopatra's "My Certificates" view I get the following error

An error occurred while trying to change the passphrase.
The output from /usr/bin/gpg was: gpg: using character set `utf-8' Secret key is available. gpg: using PGP trust model gpg: 
[...]
Heinz Wiesinger Key is protected. gpg: can't query passphrase in batch mode Can't edit this key: bad passphrase Key not changed so no update needed

I think the clue is "bad passphrase" here, because kmail reports the same when trying to sign emails. I already tried the various suggestions on the net regarding gpg-agent, but it didn't help either.
Comment 1 subscryer 2010-04-14 11:27:28 UTC
I can confirm this with an X509 certificate, I was prompted for a password to protect the certificate and no matter what password I enter (even a blank one) it won't match later either in kleopatra or kmail.
Kleopatra 2.0.12
Kde 4.4.2
Comment 2 subscryer 2010-04-20 13:43:43 UTC
This problem is fixed with gnupg 2.0.15, however it is necessary to delete the certificate and re-import it after the update (a reboot or a restart of gpg-agent is needed).
If the original reporter confirms the bug should be closed.
Comment 3 Andre Heinecke 2013-05-08 08:09:42 UTC
I'm resolving this as worksforme to keep the bugtracker clean. It works for me and as subscryer wrote this was fixed in gnupg. Thanks.