GNOME Bugzilla – Bug 167280
crash during glade interface creation
Last modified: 2005-03-03 11:06:54 UTC
Distribution: Slackware Slackware 10.1.0 Package: glade Severity: normal Version: GNOME2.6.2 2.6.0 Gnome-Distributor: GNOME.Org Synopsis: crash during glade interface creation Bugzilla-Product: glade Bugzilla-Component: general Bugzilla-Version: 2.6.0 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: while deleting a scrolledwindow located in a tabnote widget, glade crashed Steps to reproduce the crash: doesn't reproduce systematically 1. 2. 3. Expected Results: How often does this happen? 1 Additional Information: sorry guys :-( Debugging Information: Backtrace was generated from '/usr/bin/glade-2' (no debugging symbols found) Using host libthread_db library "/lib/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) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 7325)] 0x40a88488 in waitpid () from /lib/libpthread.so.0
+ Trace 55658
Thread 1 (Thread 16384 (LWP 7325))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-13 12:03 ------- Unknown version 2.6.0 in product glade. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "glade". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was effel.linux@free.fr. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
This may be a duplicate of bug 119635, which was a bug in gail. What version of gail do you have? I think the problem was fixed in 1.5.0.
Matches the stack trace in bug 167951 as well...
Yes, I'll mark as a duplicate. Note that Glade turns accessibility on, so it probably is enabled in this case. The stack trace looks a bit messy, but I'd guess that something in the destruction code is making it try to create a new accessible object for the scrolled window. Actually, looking at the code, I bet the problem is in gail_scrolled_window_scrollbar_visibility_changed(). The calls to gtk_widget_get_accessible() may be causing the problem. Maybe you need to check if the scrolled window is being destroyed at the top of the function. *** This bug has been marked as a duplicate of 167951 ***