GNOME Bugzilla – Bug 409553
crash in Terminal: Trying to create a new p...
Last modified: 2007-02-21 13:14:29 UTC
Version: 2.16.0 What were you doing when the application crashed? Trying to create a new profile. I'd renamed Default to Cominod, then applied a background colour change. I'd then realised that Default no longer existed so tried to create a new Default profile based on Cominod (I could then undo the colour change and end up where I wanted to be!) 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.19-1.2895.fc6 #1 SMP Wed Jan 10 18:32:37 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- localuser:wallmana being added to access control list SESSION_MANAGER=local/FedoraCore6:/tmp/.ICE-unix/2503 ** (eggcups:2603): WARNING **: IPP request failed with status 1030 ** (eggcups:2603): WARNING **: IPP request failed with status 1030 error getting update info: Cannot find a valid baseurl for repo: core ** (gnome-terminal:2700): CRITICAL **: terminal_profile_new: assertion `terminal_profile_lookup (name) == NULL' failed ** (bug-buddy:2925): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 102227968 vsize: 0 resident: 102227968 share: 0 rss: 20488192 rss_rlim: 0 CPU usage: start_time: 1171879517 rtime: 0 utime: 1364 stime: 0 cutime:1291 cstime: 0 timeout: 73 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 -1209006384 (LWP 2700)] [New Thread -1215870064 (LWP 2705)] (no debugging symbols found) 0x00ab2402 in __kernel_vsyscall ()
+ Trace 111948
Thread 1 (Thread -1209006384 (LWP 2700))
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 405239 ***