GNOME Bugzilla – Bug 383571
crash in Terminal: Muckin about
Last modified: 2006-12-08 02:43:10 UTC
Version: 2.16.0 What were you doing when the application crashed? Muckin about 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.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Enabled ----------- .xsession-errors --------------------- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Max failures exceeded, exiting now Window manager warning: Invalid WM_TRANSIENT_FOR window 0x0 specified for 0x140a436 (). ** ERROR **: file orbit-object.c: line 149 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... GTK Accessibility Module initialized ** Message: Hit unexpected error "Directory not empty" while doing a file operation. Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized ** Message: Hit unexpected error "Directory not empty" while doing a file operation. ** (bug-buddy:7889): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 111890432 vsize: 0 resident: 111890432 share: 0 rss: 79331328 rss_rlim: 0 CPU usage: start_time: 1165517931 rtime: 0 utime: 45984 stime: 0 cutime:40599 cstime: 0 timeout: 5385 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' (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 -1208760624 (LWP 3267)] [New Thread -1220428912 (LWP 3272)] (no debugging symbols found) 0x00ade402 in __kernel_vsyscall ()
+ Trace 92443
Thread 1 (Thread -1208760624 (LWP 3267))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 352444 ***