GNOME Bugzilla – Bug 402072
crash in System Log: i opend X System Log
Last modified: 2007-01-29 18:36:53 UTC
Version: 2.16.0 What were you doing when the application crashed? i opend X System Log 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 19:28:18 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- /usr/lib/cups/filter/foomatic-rip: found OOo UNKNOWN PRINTER "Lexmark" OOo UNKNOWN PRINTER "Lexmark" Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x360159c (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x360159c (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Warning: more than one line! Warning: more than one line! Warning: more than one line! Warning: more than one line! ** (bug-buddy:7685): WARNING **: Couldn't load icon for Open Folder ** (bug-buddy:7700): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 44941312 vsize: 0 resident: 44941312 share: 0 rss: 14123008 rss_rlim: 0 CPU usage: start_time: 1170073774 rtime: 0 utime: 25 stime: 0 cutime:22 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 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 -1208997664 (LWP 7698)] (no debugging symbols found) 0x00194402 in __kernel_vsyscall ()
+ Trace 106262
Thread 1 (Thread -1208997664 (LWP 7698))
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 366458 ***