GNOME Bugzilla – Bug 500675
crash in System Log:
Last modified: 2007-11-30 21:33:19 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 102772736 vsize: 102772736 resident: 43782144 share: 38281216 rss: 43782144 rss_rlim: 4294967295 CPU usage: start_time: 1196434273 rtime: 743 utime: 671 stime: 72 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208785184 (LWP 19100)] (no debugging symbols found) 0x00543402 in __kernel_vsyscall ()
+ Trace 180234
Thread 1 (Thread -1208785184 (LWP 19100))
----------- .xsession-errors --------------------- Launched ok, pid = 19839 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x200045e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x200045e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 18 Minor opcode: 0 Resource id: 0x200045e ICE default IO error handler doing an exit(), pid = 19836, errno = 0 Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-18871-2138935216-1196433622 --active --geometry 141x42+0+25 --title root@sasoli:/etc/tomca --------------------------------------------------
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 ***