GNOME Bugzilla – Bug 477913
crash in System Log:
Last modified: 2007-09-25 18:49:59 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: redhat release 5 Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 267849728 vsize: 267849728 resident: 213532672 share: 18509824 rss: 213532672 rss_rlim: 4294967295 CPU usage: start_time: 1190070662 rtime: 6603 utime: 6145 stime: 458 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1208523040 (LWP 15638)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163652
Thread 1 (Thread -1208523040 (LWP 15638))
----------- .xsession-errors (9 sec old) --------------------- Minor opcode: 0 Resource id: 0x5200b06 Loading "fastestmirror" plugin Loading "fedorakmod" plugin Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading "fastestmirror" plugin Loading "fedorakmod" plugin Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-11378--1088420506-1190071782 --active --geometry 80x24+0+25 --working-directory /root --zo --------------------------------------------------
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. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 442846 ***