GNOME Bugzilla – Bug 585677
crash in Sudoku: Clicked on add tracker
Last modified: 2009-06-13 21:29:02 UTC
Version: 2.24.3 What were you doing when the application crashed? Clicked on add tracker Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.24.3 2009-06-11 (Gentoo) BugBuddy Version: 2.24.2 System: Linux 2.6.27-gentoo-r8 #6 SMP Thu Jun 4 01:57:00 GMT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Darker theme Icon Theme: Mist Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (685340 sec old) --------------------- (totem:9107): GStreamer-CRITICAL **: gst_caps_ref: assertion `GST_CAPS_REFCOUNT_VALUE (caps) > 0' failed /root/.gtkrc-2.0:2: Unable to find include file: "(null)/Default-4.0/gtk-2.0/gtkrc" /root/.gtkrc-2.0:2: Unable to find include file: "(null)/Default-4.0/gtk-2.0/gtkrc" (svg:9120): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (svg:9120): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (svg:9120): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. xfce-mcs-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. gnome-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. -------------------------------------------------- Traceback (most recent call last):
+ Trace 215994
self.main_ui.gsd.get_tracker_color(tracker_id),
arr = pb.get_pixels_array()
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 416249 ***