GNOME Bugzilla – Bug 609124
crash in Sticky Notes: clicked on "New Note" in...
Last modified: 2011-06-17 20:09:11 UTC
What were you doing when the application crashed? clicked on "New Note" in a clean gnome desktop Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.27.9 #5 SMP PREEMPT Wed Jan 20 10:51:40 BRST 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 42115072 vsize: 42115072 resident: 13451264 share: 10981376 rss: 13451264 rss_rlim: 18446744073709551615 CPU usage: start_time: 1265402891 rtime: 31 utime: 28 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/gnome-applets/stickynotes_applet' [Thread debugging using libthread_db enabled] 0xb7fad424 in __kernel_vsyscall ()
+ Trace 220439
Thread 1 (Thread 0xb6c9e750 (LWP 23947))
A debugging session is active. Inferior 1 [process 23947] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** Gtk **: gtk_image_set_from_stock: assertion `GTK_IS_IMAGE (image)' failed ** Gtk **: gtk_image_set_from_stock: assertion `GTK_IS_IMAGE (image)' failed ** Gtk **: gtk_image_set_from_stock: assertion `GTK_IS_IMAGE (image)' failed ** Gtk **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_window_set_title: assertion `GTK_IS_WINDOW (window)' failed ** Gtk **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed ** Gtk **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_widget_get_modifier_style: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: gtk_widget_get_colormap: assertion `GTK_IS_WIDGET (widget)' failed ** Gdk **: gdk_colormap_alloc_colors: assertion `GDK_IS_COLORMAP (colormap)' failed ----------- .xsession-errors (8484 sec old) --------------------- This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 293979 error_code 9 request_code 55 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) opera: Plug-in 8622 is not responding. It will be closed. opera: Define environment variable OPERA_KEEP_BLOCKED_PLUGIN to keep blocked plug-ins. Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a7 specified for 0x3200003 (Welcome to). Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00003 (Authentica) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00003 (Authentica) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 and reopen this bug or report a new one. Thanks in advance!
*** Bug 610193 has been marked as a duplicate of this bug. ***
Created attachment 155304 [details] stack trace generated with "thread apply all bt" and debug symbols for all libraries
I generated stack trace (attchment id=155304) for this problem with following libraries installed: gnome-applets-2.28.0 glib2-2.22.4 gtk+2-2.18.7 libbonoboui-2.24.2 Please let me know if you need additional information or if you want me to perform other steps to track down this problem. Regards, Łukasz
Additional info: (gdb) print rc_style $1 = (GtkRcStyle *) 0x0 Regards, Łukasz
I tried to debug it and this is what is happening on my system: strace shows that gtk_builder_add_from_file in stickynotes.c:102 opens an .ui file correctly note->w_window is set to 0x0 after GTK_WIDGET call in line 104. This causes lots of error messages like: (stickynotes_applet:2583): Gtk-CRITICAL **: gtk_window_set_screen: assertion `GTK_IS_WINDOW (window)' failed and final crash in stickynotes.c:480 where NULL note->m_windows is referenced for the first time. I checked /usr/share/gnome-applets/builder/stickynotes.ui on my system and it has "stickynote_window" element defined. Digging it more I found, that gtk_builder_add_from_file returns 0 and tmp_error in gtkbuilder.c:683 is set to: 0x8209be0 "Duplicate object id 'vbox1' on line 597 (previously on line 478)" Renaming one of those triggered next duplicate object id named "label1" and renaming this one makes sticky notes to work again. Temporary workaround for this is to rename vbox1 to vbox99 in line 597 and label1 to label99 in line 616 in file builder/stickynotes.ui Regards, Łukasz
*** Bug 615864 has been marked as a duplicate of this bug. ***
looks duplicate of bug 584985
*** This bug has been marked as a duplicate of bug 594797 ***