GNOME Bugzilla – Bug 136100
Gnobots crashes on exit
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: gnome-games Severity: normal Version: GNOME2.4.1 2.4.2 Gnome-Distributor: Debian Synopsis: Gnobots crashes on exit Bugzilla-Product: gnome-games Bugzilla-Component: gnobots2 Bugzilla-Version: 2.4.2 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Crash on exit Steps to reproduce the crash: 1. Open gnobots2 2. Close gnobots2 3. Expected Results: No crash How often does this happen? Everytime Additional Information: Debugging Information: Backtrace was generated from '/usr/games/gnobots2' (no debugging symbols found)... ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-03 14:47 ------- Unknown version 2.4.2 in product gnome-games. Setting version to the default, "unspecified". The original reporter (rl@brabbel.net) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-games-maint@bugzilla.gnome.org.
Confirming this in gnobots-2.4.2, and providing a rather pathetic stack trace..... ------------------------ Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 4838)] 0x40c700cc in signgam () from /lib/libc.so.6 (gdb) thread apply all bt
+ Trace 44791
Thread 1 (Thread 16384 (LWP 4838))
Thanks for reporting the bug. The bugsquad could not confirm that this is a bug, opening and closing gnobots2-2.4.2 works okay. I am also using 2.4.2 but I cannot reproduce this bug using your steps. Can you provide more details about how to reproduce the bug? The stacktrace is incomplete, please provide a complete stacktrace, follow this address to get information on how to obtain a complete stacktrace: http://bugzilla.gnome.org/getting-traces.cgi ChangeLog: OS: Changed to Linux OS Details: Debian Keywords: Added bugsquad, GNOMEVER2.4 Version: Changed to 2.4.x State: Changed to NEEDINFO
I didn't report the fact that I am using a glib-2.3.3/gtk+-2.3.4 (gnome 2.5) system.... Have not tested it with "stable" glib/gtk/gnome.
Good news... I am not seeing this bug under gtk+-2.3.5 & co.
This is probably a duplicate of bug #123488 (it is a race condition, so changes in glib will affect whether it happens or not). I never backported the changes from 2.5. I've added it to the list for a possible 2.4.4. This may happen after I've got the last of the 2.6 bugs sorted out. *** This bug has been marked as a duplicate of 123488 ***