GNOME Bugzilla – Bug 487709
crash in Terminal: Configuring Terminal Pre...
Last modified: 2007-10-28 23:43:58 UTC
Version: 2.18.1 What were you doing when the application crashed? Configuring Terminal Preferences 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 66560000 vsize: 66560000 resident: 26734592 share: 19304448 rss: 26734592 rss_rlim: 4294967295 CPU usage: start_time: 1192665799 rtime: 304 utime: 282 stime: 22 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 -1208506128 (LWP 3505)] [New Thread -1214821488 (LWP 3509)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170988
Thread 1 (Thread -1208506128 (LWP 3505))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3192 Window manager warning: Lost connection to the display ':0.0'; most likely the X server was shut down or you killed/destroyed the window manager. (gnome-help:3533): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed ** (gnome-terminal:3505): 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 ***