Red Hat Bugzilla – Bug 190928
seahorse cannot sign keys
Last modified: 2007-11-30 17:11:32 EST
Description of problem:
Signing keys does not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Try to sign a key.
Depending on how seahorse is launched.
From menu, nothing happens.
From shell, an requester with error is opened and the following print
occur (in the shell terminal):
** (seahorse:5772): CRITICAL **: file seahorse-key-op.c: line 360
(sign_transit): should not be reached
** (seahorse:5772): CRITICAL **: edit_key: assertion `GPG_IS_OK (err)' failed
The key should be signed.
First of all, it seems there is a different behaviour depending
on how seahorse is launched: from shell it is more "verbose" and
it reports the error in a better way.
Second, this seems to be an incompatibillity of version 0.8 with
gpg 1.4.2, fixed in version 0.8.1, so upgrading should be enough.
see if this is okay in FC-4, now.
I just put 0.8.1 through the build system.
(In reply to comment #1)
> see if this is okay in FC-4, now.
> I just put 0.8.1 through the build system.
Ops, I updated all the machine to FC5, so I cannot test it for FC4.
In any case, a seahorse 8.1 will be welcome also for FC5.
0.8.1 should be available in FC5 shortly.
just waiting on the next extras push.