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 327320 - Panel crash chossing loading new logout and shutdown alert
Panel crash chossing loading new logout and shutdown alert
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: panel
git master
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 328822 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-17 11:17 UTC by Luca Ferretti
Modified: 2006-01-27 13:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Luca Ferretti 2006-01-17 11:17:23 UTC 
Steps to reproduce:
1. Select Desktop -> Logout (or Shut Down)
2. The message dialog appears, but empty
3. The "application exits unexpectly" appears


Stack trace:
Backtrace was generated from '/opt/gnome2/bin/gnome-panel'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1227052832 (LWP 1910)]
[New Thread -1229718608 (LWP 1913)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 65278

Thread 2 (Thread -1229718608 (LWP 1913))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_context_iterate
    at gmain.c line 2849
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 792
  • #3 <signal handler called>
  • #4 IA__g_logv
    at gmessages.c line 503
  • #5 IA__g_log
  • #6 IA__g_assert_warning
    at gmessages.c line 552
  • #7 gtk_message_dialog_get_property
    at gtkmessagedialog.c line 244
  • #8 IA__g_object_get_valist
    at gobject.c line 657
  • #9 IA__g_object_get
    at gobject.c line 1196
  • #10 relay_gnome_signal
    at gnome-ui-init.c line 357
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2404
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #13 IA__g_signal_emit
    at gsignal.c line 2241
  • #14 IA__gtk_widget_show
    at gtkwidget.c line 2049
  • #15 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 IA__g_closure_invoke
    at gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #18 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #19 IA__g_signal_emit
    at gsignal.c line 2241
  • #20 IA__gtk_widget_activate
    at gtkwidget.c line 3766
  • #21 IA__gtk_menu_shell_activate_item
    at gtkmenushell.c line 1057
  • #22 gtk_menu_shell_button_release
    at gtkmenushell.c line 663
  • #23 gtk_menu_button_release
    at gtkmenu.c line 2571
  • #24 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #25 g_type_class_meta_marshal
    at gclosure.c line 567
  • #26 IA__g_closure_invoke
    at gclosure.c line 490
  • #27 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #28 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #29 IA__g_signal_emit
    at gsignal.c line 2241
  • #30 gtk_widget_event_internal
    at gtkwidget.c line 3735
  • #31 IA__gtk_propagate_event
    at gtkmain.c line 2175
  • #32 IA__gtk_main_do_event
    at gtkmain.c line 1412
  • #33 gdk_event_dispatch
    at gdkevents-x11.c line 2291
  • #34 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #35 g_main_context_iterate
    at gmain.c line 2547
  • #36 IA__g_main_loop_run
    at gmain.c line 2751
  • #37 IA__gtk_main
    at gtkmain.c line 991
  • #38 main
    at main.c line 84 






Comment 1


Luca Ferretti





          2006-01-17 11:18:23 UTC
        



Please note the log_level=G_LOG_LEVEL_ERROR, not G_LOG_LEVEL_CRITICAL 






Comment 2


Vincent Untz





          2006-01-17 19:43:18 UTC
        



Ok. So, it probably happens for people using esound. Sigh. Let's look for a workaround.






Comment 3


Luca Ferretti





          2006-01-17 20:53:06 UTC
        



True. Disabling sound server in Sound capplet and killing esd process, alerts appear.






Comment 4


Vincent Untz





          2006-01-17 21:54:25 UTC
        



2006-01-17  Vincent Untz  <vuntz@gnome.org>

	Fix crash with logout dialogs when esd and sound events are enabled.
	Fix bug #327320.

	* panel-logout.c: (panel_logout_set_property): new
	(panel_logout_get_property): new
	(panel_logout_class_init): override the "message-type" property of
	GtkMessageDialog, so that our code is called when libgnomeui reads
	the property (and not gtk+ code).






Comment 5


Vincent Untz





          2006-01-27 13:01:15 UTC
        



*** Bug 328822 has been marked as a duplicate of this bug. ***