GNOME Bugzilla – Bug 413401
crash in Terminal: i pressed CTRL+T to open...
Last modified: 2007-03-01 11:26:43 UTC
Version: 2.17.92 What were you doing when the application crashed? i pressed CTRL+T to open new window Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.92 2007-02-27 (Red Hat, Inc) BugBuddy Version: 2.17.4 System: Linux 2.6.20-1.2953.fc7 #1 SMP Mon Feb 26 21:30:41 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 97992704 vsize: 97992704 resident: 15261696 share: 10899456 rss: 15261696 rss_rlim: 4294967295 CPU usage: start_time: 1172747431 rtime: 27 utime: 21 stime: 6 cutime:0 cstime: 0 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208875296 (LWP 3408)] [New Thread -1215226992 (LWP 3412)] (no debugging symbols found) 0x0041d402 in __kernel_vsyscall ()
+ Trace 114875
Thread 1 (Thread -1208875296 (LWP 3408))
----------- .xsession-errors --------------------- (gnome-terminal:3408): Vte-WARNING **: Can not find appropiate font for character U+ac01. (gnome-terminal:3408): Vte-WARNING **: Can not find appropiate font for character U+ac04. (gnome-terminal:3408): Vte-WARNING **: Can not find appropiate font for character U+ac08. (gnome-terminal:3408): Vte-WARNING **: Can not find appropiate font for character U+ac10. GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
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. *** This bug has been marked as a duplicate of 413036 ***