GNOME Bugzilla – Bug 316998
sol crashed unexpectedly, had been up for 8 hours, YAST2 online update of linux utilities and openOffice
Last modified: 2012-01-31 23:23:02 UTC
Distribution: SuSE Linux 9.3 (i586) Package: gnome-games Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: SUSE Synopsis: sol crashed unexpectedly, had been up for 8 hours, YAST2 online update of linux utilities and openOffice Bugzilla-Product: gnome-games Bugzilla-Component: aisleriot Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: sol crashed - not much going on (samba in background) openoffice updated earlier, sol up since before then Steps to reproduce the crash: 1. ? 2. 3. Expected Results: How often does this happen? first time Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/sol' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1090412768 (LWP 12309)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x409b2dce in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 63152
Thread 1 (Thread 1090412768 (LWP 12309))
------- Bug moved to this database by unknown@gnome.bugs 2005-09-23 05:23 UTC ------- Unknown version 2.10.0 in product gnome-games. Setting version to "2.10.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was hauser.dnai@rcn.com.
That is a *very* interesting stack trace. An expose event on a box is failing the assertion child->parent == GTK_WIDGET (container) which suggests that the data for that container is severly fucked up. Also, the stack contains calls like: gtk_window_new bonobo_dock_new and gtk_toolbar_set_drop_highlight_item which sort-of suggests that it occurs during the detachment of a tear-off toolbar. (We had a tear-off grip on the toolbar in 2.10.) Not sure what to make of this.
This looks like a GTK+ bug related to the update process. See bug #305680. Unfortunately no one seems to have fixed it. *** This bug has been marked as a duplicate of 305680 ***
This bug is being reassigned to the "general" component so we can close the aisleriot bugzilla component. Apologies for the mass email!