GNOME Bugzilla – Bug 387132
crash in Terminal:
Last modified: 2006-12-18 19:03:24 UTC
Version: 2.16.0 What were you doing when the application crashed? 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.2849.fc6 #1 SMP Fri Nov 10 12:34:46 EST 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled ----------- .xsession-errors (1479977 sec old) --------------------- compiz: Couldn't bind redirected window 0x240000d to texture compiz: pixmap 0x10006f4 can't be bound to texture compiz: Couldn't bind redirected window 0x240000d to texture compiz: pixmap 0x10006f4 can't be bound to texture compiz: Couldn't bind redirected window 0x240000d to texture compiz: pixmap 0x10006f4 can't be bound to texture compiz: Couldn't bind redirected window 0x240000d to texture compiz: pixmap 0x10006f4 can't be bound to texture compiz: Couldn't bind redirected window 0x240000d to texture compiz: pixmap 0x10006f4 can't be bound to texture compiz: Couldn't bind redirected window 0x240000d to texture compiz: pixmap 0x10006f4 can't be bound to texture compiz: Couldn't bind redirected window 0x240000d to texture ...Too much output, ignoring rest... -------------------------------------------------- Memory status: size: 365088768 vsize: 365088768 resident: 27643904 share: 7532544 rss: 27643904 rss_rlim: -1 CPU usage: start_time: 1164962509 rtime: 19268 utime: 16100 stime: 3168 cutime:261 cstime: 262 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-terminal' (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 46912520399568 (LWP 8764)] [New Thread 1084229952 (LWP 8778)] (no debugging symbols found) 0x0000003dbe40d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 95111
Thread 1 (Thread 46912520399568 (LWP 8764))
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 348979 ***