GNOME Bugzilla – Bug 459031
crash in Sudoku: Installing gutsy gibbon ...
Last modified: 2007-07-25 23:27:39 UTC
What were you doing when the application crashed? Installing gutsy gibbon and tried starting sudoku Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.5 2007-07-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human 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 (19 sec old) --------------------- ** (update-notifier:8246): WARNING **: no cdrom: disk ** (update-notifier:8246): WARNING **: no cdrom: disk Window manager warning: last_focus_time (3921288462) is greater than comparison timestamp (3903520862). This most likely represents a buggy client sending inaccurate timestamps in messages such as _N Window manager warning: last_user_time (3921287835) is greater than comparison timestamp (3903520862). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE Window manager warning: 0x100001e (Desktop) appears to be one of the offending windows with a timestamp of 3920823751. Working around... Window manager warning: 0xc0001c (Top Expand) appears to be one of the offending windows with a timestamp of 3921039547. Working around... Window manager warning: 0x2a000d8 (/bin/false) appears to be one of the offending windows with a timestamp of 3921140951. Working around... ***MEMORY-WARNING***: gnome-sudoku[26533]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this p ImportError: could not import gnomecanvas -------------------------------------------------- ImportError: could not import gnomecanvas
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 452748 ***