GNOME Bugzilla – Bug 600756
crash in Sticky Notes: I have no idea what just...
Last modified: 2009-11-04 23:37:30 UTC
What were you doing when the application crashed? I have no idea what just happened, as I switched VTs while logging in Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-09-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.30-simes-9.0 #1 PREEMPT Wed Jul 29 15:03:26 NZST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: Lush GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 38850560 vsize: 38850560 resident: 12886016 share: 10805248 rss: 12886016 rss_rlim: 18446744073709551615 CPU usage: start_time: 1257377536 rtime: 51 utime: 44 stime: 7 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] 0xb7eff424 in __kernel_vsyscall ()
+ Trace 218810
Thread 1 (Thread 0xb6a9f760 (LWP 4097))
Inferior 1 [process 4097] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** Gtk **: gtk_window_resize: assertion `GTK_IS_WINDOW (window)' failed ** Gtk **: gtk_window_move: assertion `GTK_IS_WINDOW (window)' 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_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 ----------- .xsession-errors (41 sec old) --------------------- ** (gnome-volume-control-applet:3556): WARNING **: Unable to get default source Unable to open desktop file /usr/share/applications/kde/konqbrowser.desktop for panel launcher: No such file or directory Unable to open desktop file /home/brendon/Desktop/ies4linux-ie7.desktop for panel launcher: No such file or directory Unable to open desktop file /home/brendon/Desktop/ies4linux-ie6.desktop for panel launcher: No such file or directory Unable to open desktop file /home/brendon/Desktop/ies4linux-ie55.desktop for panel launcher: No such file or directory Unable to open desktop file /home/brendon/Desktop/ies4linux-ie5.desktop for panel launcher: No such file or directory Unable to open desktop file /home/brendon/Desktop/ies4linux-ie2.desktop for panel launcher: No such file or directory Unable to open desktop file /home/brendon/Desktop/ies4linux-ie15.desktop for panel launcher: No such file or directory Unable to open desktop file /home/brendon/Desktop/ies4linux-ie1.desktop for panel launcher: No such file or directory ** (gnome-screensaver:4207): WARNING **: screensaver already running in this session (nautilus:3519): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blo (nautilus:3521): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blo --------------------------------------------------
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 bug 584985 ***