GNOME Bugzilla – Bug 412886
crash in Glade Interface Designer: i was trying to open a C...
Last modified: 2007-04-12 20:48:59 UTC
What were you doing when the application crashed? i was trying to open a C header file, when i selected the file, it crashed Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 88801280 vsize: 0 resident: 88801280 share: 0 rss: 22282240 rss_rlim: 0 CPU usage: start_time: 1172625901 rtime: 0 utime: 1564 stime: 0 cutime:612 cstime: 0 timeout: 952 it_real_value: 0 frequency: 0 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) [Thread debugging using libthread_db enabled] [New Thread -1208239904 (LWP 2974)] (no debugging symbols found) 0x00aed402 in __kernel_vsyscall ()
+ Trace 114505
Thread 1 (Thread -1208239904 (LWP 2974))
----------- .xsession-errors (6 sec old) --------------------- I/O warning : failed to load external entity "/root/.glade2" Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. (glade-2:2974): XML-CRITICAL **: Start tag expected, '<' not found ** (glade-2:2974): WARNING **: did not finish in PARSER_FINISH state! ** ERROR **: file gailtreeview.c: line 3604 (garbage_collect_cell_data): assertion failed: (GAIL_IS_TREE_VIEW (data)) aborting... GTK Accessibility Module initialized GTK Accessibility Module initialized ** (bug-buddy:3031): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 325759 ***