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 609856 - crash in Verify Signature: Opening an Encrypted mes...
crash in Verify Signature: Opening an Encrypted mes...
Status: RESOLVED DUPLICATE of bug 607423
Product: seahorse
Classification: Applications
Component: general
2.28.x
Other All
: Normal critical
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2010-02-13 17:56 UTC by dabbott
Modified: 2010-02-14 04:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description dabbott 2010-02-13 17:56:02 UTC 
Version: 2.28.1

What were you doing when the application crashed?
Opening an Encrypted message


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.28.2 2010-01-13 (Gentoo)
BugBuddy Version: 2.28.0

System: Linux 2.6.32-gentoo-r3 #1 SMP Wed Feb 3 04:57:49 EST 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10704901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks Gentoo
Icon Theme: gnome-noble
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 218955776 vsize: 218955776 resident: 20062208 share: 13254656 rss: 20062208 rss_rlim: 18446744073709551615
CPU usage: start_time: 1266083715 rtime: 7 utime: 4 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/seahorse-tool'

[Thread debugging using libthread_db enabled]
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
0x00007f135d982b8e in __libc_waitpid (pid=<value optimized out>, stat_loc=
    0x7fff39c1c710, options=<value optimized out>)
    at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 220560

Thread 1 (Thread 0x7f135f481780 (LWP 22492))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 IA__g_spawn_sync
    at gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #3 bugbuddy_segv_handle(int)
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 _gpgme_release_result
    at gpgme.c line 229
  • #6 _gpgme_op_reset
    at op-support.c line 80
  • #7 decrypt_verify_start
    at decrypt-verify.c line 51
  • #8 decrypt_start
    at seahorse-tool.c line 525
  • #9 step_operation
    at seahorse-tool-files.c line 787
  • #10 seahorse_tool_files_process
    at seahorse-tool-files.c line 895
  • #11 main
    at seahorse-tool.c line 749 

	Inferior 1 [process 22492] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** seahorse-tool **: seahorse_pgp_operation_init: assertion `GPG_IS_OK (err)' failed 


----------- .xsession-errors (317327 sec old) ---------------------
(firefox:7204): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7204): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7204): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7204): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7204): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7204): Gdk-WARNING **: XID collision, trouble ahead
(firefox:7204): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2010-02-14 04:39:19 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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