GNOME Bugzilla – Bug 328822
Panel crashes upon selecting Logout / Shutdown
Last modified: 2006-01-27 13:01:15 UTC
Installed Opensolaris 2.13 gnome on snv_31. Selecting Logout or Shutdown from menu or panel applet causes gnome panel to crash. This is reproducible 95% of the tries.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Attaching the stack trace: [1] _waitid(0xe20, 0x8045c14, 0x0, 0x0), at 0xd27699c5 [2] _waitpid(0xe20, 0x8045c14, 0x0), at 0xd27358ef [3] waitpid(0xe20, 0x8045c14, 0x0), at 0xd275d297 [4] libgnomeui_segv_handle(0x5, 0x0, 0x8045cc0), at 0xd0300fb6 [5] __sighndlr(0x5, 0x0, 0x8045cc0, 0xd0300f0c), at 0xd276807f [6] call_user_handler(0x5, 0x0, 0x8045cc0), at 0xd275de00 [7] sigacthandler(), at 0xd275df88 ---- called from signal handler with signal 5 (SIGTRAP) ------ [8] __lwp_kill(0x1, 0x5), at 0xd2769595 [9] pthread_kill(0x1, 0x5), at 0xd2766150 [10] raise(0x5), at 0xd272e144 [11] g_logv(0xd01f37ec, 0x4, 0xd01f39a8, 0x80463ac), at 0xd2530e99 [12] g_log(0xd01f37ec, 0x4, 0xd01f39a8, 0xd01f3a48, 0xf4), at 0xd2530f61 [13] gtk_message_dialog_get_property(0x83c5c60, 0x1, 0x804640c, 0x81bf800), at 0xd0093f58 [14] g_object_get_valist(0x83c5c60, 0xd03309a0, 0x80464c0), at 0xd24af0d8 [15] g_object_get(0x83c5c60, 0xd03309a0, 0x80464f8, 0x0), at 0xd24af3f0 [16] relay_gnome_signal(0x804653c, 0x1, 0x80465dc, 0x0), at 0xd0300583 [17] signal_emit_unlocked_R(0x8189610, 0x0, 0x83c5c60, 0x0, 0x80465dc), at 0xd 24bf9b6 [18] g_signal_emit_valist(0x83c5c60, 0x16, 0x0, 0x8046848), at 0xd24bede5 [19] g_signal_emit(0x83c5c60, 0x16, 0x0), at 0xd24bef81 [20] gtk_widget_show(0x83c5c60), at 0xd01636aa [21] panel_logout_new(0x1), at 0x80dc470 [22] panel_action_shutdown(0x84a5e18, 0x0), at 0x80bf9a5 [23] g_cclosure_marshal_VOID__VOID(0x84a6b68, 0x0, 0x1, 0x8046a1c, 0x804697c, 0x0), at 0xd24c02dd [24] g_closure_invoke(0x84a6b68, 0x0, 0x1, 0x8046a1c, 0x804697c), at 0xd24aa8a 6 [25] signal_emit_unlocked_R(0x8195700, 0x0, 0x84a5e18, 0x0, 0x8046a1c), at 0xd 24bfb5c [26] g_signal_emit_valist(0x84a5e18, 0x62, 0x0, 0x8046c88), at 0xd24bede5 [27] g_signal_emit(0x84a5e18, 0x62, 0x0), at 0xd24bef81 [28] gtk_widget_activate(0x84a5e18), at 0xd0165c78 [29] gtk_menu_shell_activate_item(0x82b48c8, 0x84a5e18, 0x1), at 0xd00920de [30] gtk_menu_shell_button_release(0x82b48c8, 0x83e1c68), at 0xd0091555 [31] gtk_menu_button_release(0x82b48c8, 0x83e1c68, 0x8188948), at 0xd008a6fb [32] _gtk_marshal_BOOLEAN__BOXED(0x8189c10, 0x8046e30, 0x2, 0x8046eec, 0x8046e 4c, 0xd008a6a4), at 0xd0083fb9 [33] g_type_class_meta_marshal(0x8189c10, 0x8046e30, 0x2, 0x8046eec, 0x8046e4c , 0xb4), at 0xd24aaba1 [34] g_closure_invoke(0x8189c10, 0x8046e30, 0x2, 0x8046eec, 0x8046e4c), at 0xd 24aa8a6 [35] signal_emit_unlocked_R(0x8190fa0, 0x0, 0x82b48c8, 0x804706c, 0x8046eec), at 0xd24bfd21 [36] g_signal_emit_valist(0x82b48c8, 0x2b, 0x0, 0x8047160), at 0xd24beb7b [37] g_signal_emit(0x82b48c8, 0x2b, 0x0, 0x83e1c68, 0x8047184), at 0xd24bef81 [38] gtk_widget_event_internal(0x82b48c8, 0x83e1c68), at 0xd0165aea [39] gtk_widget_event(0x82b48c8, 0x83e1c68), at 0xd0165779 [40] gtk_propagate_event(0x82b48c8, 0x83e1c68), at 0xd0082b2e [41] gtk_main_do_event(0x83e1c68, 0x0), at 0xd0081ba0 [42] gdk_event_dispatch(0x812ee30, 0x0, 0x0), at 0xd264e0e6 [43] g_main_dispatch(0x812ee78), at 0xd2529418 [44] g_main_context_dispatch(0x812ee78), at 0xd252a501 [45] g_main_context_iterate(0x812ee78, 0x1, 0x1, 0x8115238), at 0xd252a921 [46] g_main_loop_run(0x82b2048), at 0xd252af26 [47] gtk_main(), at 0xd00814c3 [48] main(0x3, 0x80473d4, 0x80473e4), at 0x809a0d2
This is already fixed in HEAD. Workaround is to disable sound events. *** This bug has been marked as a duplicate of 327320 ***