After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 600804 - seahorse-tool crash when trying to sign a file
seahorse-tool crash when trying to sign a file
Status: RESOLVED DUPLICATE of bug 607423
Product: seahorse
Classification: Applications
Component: general
2.28.x
Other Linux
: Normal critical
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2009-11-05 11:16 UTC by Michał Sawicz
Modified: 2010-05-14 15:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
seahorse-tool backtrace (13.56 KB, text/plain)
2009-11-05 11:16 UTC, Michał Sawicz
Details
Backtrace for seahorse-tool signing crash (3.89 KB, text/plain)
2009-11-17 05:00 UTC, Dave Wheeler
Details

Description Michał Sawicz 2009-11-05 11:16:38 UTC
Created attachment 146996 [details]
seahorse-tool backtrace

The seahorse-tool crashes with

** (seahorse-tool:13479): CRITICAL **: prompt_signer: assertion `GPG_IS_OK
(gerr)' failed

when trying to sign a file:

$ seahorse-tool -s <filename>

I have generated a gdb backtrace according to
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/227493/comments/9

This is on openSUSE 11.2RC2 with following versions of relevant software:

seahorse 2.28.0
gpgme 1.2.0
gpg-error 1.7
gpg2 2.0.12
gnome 2.28.0

This means I can't sign nor verify anything using seahorse.
Comment 1 Pablo Castellano (IRC: pablog) 2009-11-05 12:15:47 UTC
Hello Michał:
It seems to be a problem with:

        gerr = gpgme_new (&ctx);

that returns some error that I cannot see because the values are optimized.
Can you recompile seahorse-plugins with --enable-debug flag?

Thanks.
Comment 2 Michał Sawicz 2009-11-05 13:03:11 UTC
Not really, I'm getting:

cc1: warnings being treated as errors
seahorse-operation.c: In function 'multi_operation_progress':
seahorse-operation.c:397: error: cast from pointer to integer of different size
seahorse-operation.c:438: error: cast from pointer to integer of different size
seahorse-operation.c: In function 'multi_operation_done':
seahorse-operation.c:460: error: cast from pointer to integer of different size
seahorse-operation.c:460: error: cast from pointer to integer of different size
seahorse-operation.c:475: error: cast from pointer to integer of different size
seahorse-operation.c: In function 'seahorse_multi_operation_take':
seahorse-operation.c:578: error: cast from pointer to integer of different size
seahorse-operation.c:582: error: cast from pointer to integer of different size
seahorse-operation.c:582: error: cast from pointer to integer of different size
make[3]: *** [seahorse-operation.o] Error 1
make[3]: Leaving directory `/usr/src/packages/BUILD/seahorse-plugins-2.28.0/libseahorse'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/packages/BUILD/seahorse-plugins-2.28.0/libseahorse'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/packages/BUILD/seahorse-plugins-2.28.0'
make: *** [all] Error 2

when building with --enable-debug. I thought --enable-fatal-messages would help, but it didn't...
Comment 3 Dave Wheeler 2009-11-17 05:00:12 UTC
Created attachment 147951 [details]
Backtrace for seahorse-tool signing crash

I'm getting the same error. I was able to recompile with the --enable-debug flag, and am attaching my backtrace.

I'm also experiencing the same issue with decrypting and encrypting operations.
Comment 4 Stefano Costa 2010-02-28 18:01:11 UTC
Looks like this bug, #607423 and #605888 are actually the same bug ?
Comment 5 Michał Sawicz 2010-05-14 01:12:56 UTC
This is still valid on latest openSUSE Factory.
Comment 6 Michał Sawicz 2010-05-14 01:37:59 UTC
This is fixed by the patch available on this bug https://bugzilla.gnome.org/show_bug.cgi?id=607423
Comment 7 Wouter Bolsterlee (uws) 2010-05-14 15:45:28 UTC

*** This bug has been marked as a duplicate of bug 607423 ***