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 605696 - crash in Verify Signature: Had Nautilus open and at...
crash in Verify Signature: Had Nautilus open and at...
Status: RESOLVED DUPLICATE of bug 607423
Product: seahorse
Classification: Applications
Component: general
2.28.x
Other All
: High critical
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2009-12-29 20:27 UTC by dabbott
Modified: 2010-01-19 10:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description dabbott 2009-12-29 20:27:49 UTC
Version: 2.28.1

What were you doing when the application crashed?
Had Nautilus open and attempted to view a .gpg file.


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.28.0 2009-11-07 (Gentoo)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-gentoo-r5 #2 SMP Wed Aug 19 20:55:57 EDT 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10703000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks Gentoo
Icon Theme: gnome-noble
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 220327936 vsize: 220327936 resident: 19578880 share: 12877824 rss: 19578880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1262118382 rtime: 7 utime: 3 stime: 4 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.2-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
0x00007f1f850c0b8e in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7f1f86bbd780 (LWP 19963))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 bugbuddy_segv_handle(int)
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 _gpgme_release_result
    from /usr/lib/libgpgme.so.11
  • #6 _gpgme_op_reset
    from /usr/lib/libgpgme.so.11
  • #7 decrypt_verify_start
    from /usr/lib/libgpgme.so.11
  • #8 decrypt_start
  • #9 step_operation
  • #10 seahorse_tool_files_process
  • #11 main
A debugging session is active.

	Inferior 1 [process 19963] 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 (13384448 sec old) ---------------------
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
--- Hash table keys for warning below:
--> file:///home/david/Desktop/2009-Screenshot-Contest
--> file:///home/david
--> x-nautilus-desktop:///
--> file:///home/david/Desktop/2009-Screenshot-Contest/gallery
--> file:///home/david/.thunderbird
--> file:///home/david/Desktop
--> file:///home
--> file:///home/david/.thunderbird/d6sqcw4l.default
(nautilus:3075): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 8 elements at quit time (keys above)
(nautilus:3075): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 8 elements at quit time
--------------------------------------------------
Comment 1 Akhil Laddha 2009-12-30 04:11:41 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Akhil Laddha 2010-01-19 10:29:02 UTC

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