GNOME Bugzilla – Bug 422155
crash in Glade Interface Designer: I selected a GnomeFontPi...
Last modified: 2007-04-12 20:46:31 UTC
What were you doing when the application crashed? I selected a GnomeFontPicker widget from a table, right clicked, and selected Delete. 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: 99221504 vsize: 0 resident: 99221504 share: 0 rss: 18702336 rss_rlim: 0 CPU usage: start_time: 1174708291 rtime: 0 utime: 668 stime: 0 cutime:629 cstime: 0 timeout: 39 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 -1208764192 (LWP 19048)] (no debugging symbols found) 0x004e8402 in __kernel_vsyscall ()
+ Trace 121660
Thread 1 (Thread -1208764192 (LWP 19048))
----------- .xsession-errors (39 sec old) --------------------- kdeinit: PID 27224 terminated. kdeinit: Got EXEC_NEW 'kio_http' from launcher. DCOP: register 'anonymous-4362' -> number of clients is now 2 DCOP: register 'anonymous-4381' -> number of clients is now 3 DCOP: unregister 'anonymous-4381' DCOP: unregister 'anonymous-4362' kdeinit: PID 4362 terminated. kdeinit: Got EXEC_NEW 'kio_http' from launcher. DCOP: register 'anonymous-4502' -> number of clients is now 2 DCOP: register 'anonymous-4561' -> number of clients is now 3 DCOP: unregister 'anonymous-4561' kdeinit: PID 4502 terminated. DCOP: unregister 'anonymous-4502' kdeinit: Got EXEC_NEW 'kio_http' from launcher. DCOP: register 'anonymous-4576' -> number of clients is now 2 --------------------------------------------------
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 ***