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 367486 - crash in Encryption Keys: Encryption Key Manager g...
crash in Encryption Keys: Encryption Key Manager g...
Status: RESOLVED DUPLICATE of bug 325759
Product: seahorse
Classification: Applications
Component: general
0.9.5
Other All
: High critical
: 1.0.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2006-10-30 08:54 UTC by rene
Modified: 2006-10-30 12:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rene 2006-10-30 08:54:43 UTC
What were you doing when the application crashed?
Encryption Key Manager geschlossen


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 64049152 vsize: 0 resident: 64049152 share: 0 rss: 17182720 rss_rlim: 0
CPU usage: start_time: 1162198375 rtime: 0 utime: 216 stime: 0 cutime:200 cstime: 0 timeout: 16 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226037584 (LWP 8647)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226037584 (LWP 8647))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gail_tree_view_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #11 gail_tree_view_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #12 _gtk_marshal_VOID__BOXED_BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #17 gtk_tree_model_row_inserted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_tree_model_sort_convert_iter_to_child_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 _gtk_marshal_VOID__BOXED_BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #24 gtk_tree_model_row_inserted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_tree_model_filter_convert_child_iter_to_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 _gtk_marshal_VOID__BOXED_BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #31 gtk_tree_model_row_inserted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_tree_store_insert_before
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 gtk_tree_store_append
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-30 12:20: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 325759 ***