GNOME Bugzilla – Bug 481493
crash in Terminal: create a new "Default" t...
Last modified: 2007-10-28 23:44:05 UTC
Version: 2.18.1 What were you doing when the application crashed? create a new "Default" terminal profile Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 102551552 vsize: 102551552 resident: 34742272 share: 20500480 rss: 34742272 rss_rlim: 4294967295 CPU usage: start_time: 1190963924 rtime: 1124 utime: 1031 stime: 93 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 -1208473360 (LWP 18643)] [New Thread -1252213872 (LWP 18648)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 166325
Thread 1 (Thread -1208473360 (LWP 18643))
----------- .xsession-errors --------------------- gcin XIM will use en_US.UTF-8 as the default encoding merge tsin-1.src Line 1 problem in phbufN!=chbufN 4 != 6 load_gtab_list /usr/share/gcin/table/gtab.list -- /tmp/gcin-gilbert/socket-:0.0-gcin connection via TCP is disabled Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3400003 specified for 0x34000ba (Keep Resol). (gnome-terminal:18643): Vte-WARNING **: No handler for control sequence `device-control-string' defined. compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 ** Message: Found best visual for GL: 0x24 ** (gnome-terminal:18643): CRITICAL **: terminal_profile_new: assertion `terminal_profile_lookup (name) == NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 457825 ***