GNOME Bugzilla – Bug 399449
crash in Terminal: Closing (exiting).
Last modified: 2007-01-23 08:31:57 UTC
Version: 2.16.0 What were you doing when the application crashed? Closing (exiting). 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.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled ----------- .xsession-errors (1047652 sec old) --------------------- compiz: Couldn't bind redirected window 0x2a02188 to texture compiz: pixmap 0x1200193 can't be bound to texture compiz: Couldn't bind redirected window 0x2a00a90 to texture compiz: pixmap 0x1200210 can't be bound to texture compiz: Couldn't bind redirected window 0x2a02188 to texture compiz: pixmap 0x1200193 can't be bound to texture compiz: Couldn't bind redirected window 0x2a00a90 to texture compiz: pixmap 0x1200210 can't be bound to texture compiz: Couldn't bind redirected window 0x2a02188 to texture compiz: pixmap 0x1200193 can't be bound to texture compiz: Couldn't bind redirected window 0x2a00a90 to texture compiz: pixmap 0x1200210 can't be bound to texture compiz: Couldn't bind redirected window 0x2a02188 to texture ...Too much output, ignoring rest... -------------------------------------------------- Memory status: size: 81424384 vsize: 0 resident: 81424384 share: 0 rss: 18939904 rss_rlim: 0 CPU usage: start_time: 1168437517 rtime: 0 utime: 6101 stime: 0 cutime:5138 cstime: 0 timeout: 963 it_real_value: 0 frequency: 170 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 -1208940848 (LWP 32420)] [New Thread -1215616112 (LWP 32424)] (no debugging symbols found) 0x00421402 in __kernel_vsyscall ()
+ Trace 104329
Thread 1 (Thread -1208940848 (LWP 32420))
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 353498 ***