GNOME Bugzilla – Bug 454406
crash in Sudoku: launching it
Last modified: 2007-07-07 21:10:59 UTC
What were you doing when the application crashed? launching it Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.4 2007-06-29 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome 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 --------------------- ***MEMORY-WARNING***: gnome-terminal[12042]: 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 ***MEMORY-WARNING***: firefox-bin[12299]: 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 pr *** CLB *** Initializing Google Browser Sync... *** CLB *** Instanciating core objects... *** CLB *** Registering with XPCOM... *** CLB *** Adding categories... *** CLB *** Google Browser Sync initialized succesfully! ***MEMORY-WARNING***: gnome-terminal[12428]: 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 ***MEMORY-WARNING***: gnome-sudoku[12498]: 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 TypeError: function takes exactly 0 arguments (1 given) -------------------------------------------------- TypeError: function takes exactly 0 arguments (1 given)
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 453825 ***