GNOME Bugzilla – Bug 442230
crash in Sudoku: Steps to Reproduce: 1. r...
Last modified: 2007-05-30 10:58:56 UTC
What were you doing when the application crashed? Steps to Reproduce: 1. run gnome-sudoku game 2. Click on View 3. Move toward Edit --- RH bug: Bug 241742: [Sudoku] game crashed while selecting running through menu items (View->Edit) [with BT] Actual results: Application Crashed Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.19.2 2007-05-19 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3173.fc8 #1 SMP Fri May 18 17:35:17 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 69406720 vsize: 69406720 resident: 35053568 share: 22065152 rss: 35053568 rss_rlim: 4294967295 CPU usage: start_time: 1180486144 rtime: 682 utime: 645 stime: 37 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-sudoku' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208334656 (LWP 10650)] (no debugging symbols found) 0x0068a402 in __kernel_vsyscall ()
+ Trace 136751
Thread 1 (Thread -1208334656 (LWP 10650))
----------- .xsession-errors (61542 sec old) --------------------- ** (gnibbles:6830): WARNING **: failure: no device event controller found. ** (gnibbles:6830): WARNING **: failure: no device event controller found. ** (gnibbles:6830): WARNING **: failure: no device event controller found. ** (gnibbles:6830): WARNING **: failure: no device event controller found. ...Too much output, ignoring rest... --------------------------------------------------
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. Thanks in advance!
ok, updated bt with gtk2/glibc --------- Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.19.2 2007-05-19 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3173.fc8 #1 SMP Fri May 18 17:35:17 EDT 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: 69009408 vsize: 69009408 resident: 36982784 share: 23949312 rss: 36982784 rss_rlim: 4294967295 CPU usage: start_time: 1180522209 rtime: 108 utime: 101 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-sudoku' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208215872 (LWP 10560)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x0030e402 in __kernel_vsyscall ()
+ Trace 136795
Thread 1 (Thread -1208215872 (LWP 10560))
----------- .xsession-errors --------------------- Major opcode: 20 Minor opcode: 0 Resource id: 0x1604ce3 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x1604ce3 QImage::smoothScale: Image is a null image ***MEMORY-WARNING***: gnome-sudoku[10560]: 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 /usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py:991: GtkWarning: gdk_pixbuf_new_from_file: assertion `filename != NULL' failed gtk.main() /usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py:991: Warning: g_object_ref: assertion `G_IS_OBJECT (object)' failed gtk.main() "/usr/bin/gnome-sudoku": not in executable format: File format not recognized --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 434491 ***