GNOME Bugzilla – Bug 371288
crash in Glade Interface Designer: Placing a menu toolbar. ...
Last modified: 2011-01-13 16:24:39 UTC
What were you doing when the application crashed? Placing a menu toolbar. I have no idea what went wrong. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 14:59:01 EDT 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- Could not load widget class ProxyCheckButton Could not load widget class ProxyRadioButton Could not load widget class ProxySpinButton Could not load widget class ProxyButton Could not load widget class ProxyTextView You need twisted installed to be able to reload GTK Accessibility Module initialized I/O warning : failed to load external entity "/home/josh/.glade2" Gtk-ERROR **: file gtktextview.c: line 5720 (gtk_text_view_start_selection_drag): assertion failed: (text_view->selection_drag_handler == 0) aborting... GTK Accessibility Module initialized GTK Accessibility Module initialized ** (bug-buddy:5446): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 318193664 vsize: 318193664 resident: 20226048 share: 11997184 rss: 20226048 rss_rlim: -1 CPU usage: start_time: 1162768099 rtime: 35 utime: 32 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/glade-2' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496391968 (LWP 5444)] (no debugging symbols found) 0x0000003d0de0d935 in waitpid () from /lib64/libpthread.so.0
+ Trace 83420
Thread 1 (Thread 46912496391968 (LWP 5444))
*** Bug 404490 has been marked as a duplicate of this bug. ***
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 and reopen this bug or report a new one. Thanks in advance!