Bug 113536 – seahorse crash on exit

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 113536 - seahorse crash on exit


Summary:	seahorse crash on exit


Status:	RESOLVED DUPLICATE of bug 112958

Product:	seahorse
Classification:	Applications
Component:	general
Version:	0.6.x
Hardware:	Other other

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Seahorse Maintainer
QA Contact:	Seahorse Maintainer

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-05-22 16:46 UTC by j
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description j 2003-05-22 16:46:40 UTC

Package: seahorse
Severity: normal
Version: 0.4.3
Synopsis: seahorse crash on exit
Bugzilla-Product: seahorse
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
seahorse does not quit properly	

Steps to reproduce the problem:
1. open seahorse
2. close seahorse
3. crash

Actual Results:
crash

Expected Results:
clean exit




Debugging Information:

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

[New Thread 16384 (LWP 12129)]
0x40896af9 in wait4 () from /lib/libc.so.6

+ Trace 37122

Thread 1 (Thread 16384 (LWP 12129))

#0 wait4
from /lib/libc.so.6
#1 sys_sigabbrev
from /lib/libc.so.6
#2 waitpid
from /lib/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/libpthread.so.0
#5 sigaction
from /lib/libc.so.6
#6 seahorse_sub_key_iter_removed
at seahorse-sub-key-iter.c line 109
#7 seahorse_key_iter_remove
at seahorse-key-iter.c line 212
#8 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#15 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#16 seahorse_context_finalize
at seahorse-context.c line 159
#17 g_object_class_list_properties
from /usr/lib/libgobject-2.0.so.0
#18 seahorse_widget_finalize
at seahorse-widget.c line 130
#19 g_object_class_list_properties
from /usr/lib/libgobject-2.0.so.0
#20 quit
at seahorse-key-manager.c line 50
#21 delete_event
at seahorse-key-manager.c line 59
#22 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#30 g_get_current_time
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 main
at main.c line 50
#0 wait4
from /lib/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-22 12:46 -------

The original reporter (j@thing.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, seahorse-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-05-25 03:28:26 UTC

Appears to be a unique stack trace, according to the
simple-dup-finder.     Marking severity->critical (it's a crasher),
adding bugsquad keyword, and marking as new.

Comment 2 Samuel Stringham 2004-10-04 00:05:34 UTC

The stack trace is unique, but this is the same as bug 112958.  Basically there
is a race condition on the exiting of seahorse that can be triggered by freeing
the main widget, then attempting to free to contexts (like running
seahorse_key_iter_remove).

Marking as dup.

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