GNOME Bugzilla – Bug 471970
crash in System Log:
Last modified: 2007-09-15 11:54:30 UTC
Version: 2.18.1 What were you doing when the application crashed? 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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 281112576 vsize: 281112576 resident: 23900160 share: 14626816 rss: 23900160 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188482537 rtime: 134 utime: 121 stime: 13 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496311120 (LWP 3032)] (no debugging symbols found) 0x0000003022c0d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 159177
Thread 1 (Thread 46912496311120 (LWP 3032))
----------- .xsession-errors (44 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/dvfileserver:/tmp/.ICE-unix/2830 Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory kbuildsycoca running... DCOP Cleaning up dead connections. Launched ok, pid = 3565 OggS-SEEK: at 0 want 60408 got 51136 (diff-requested 60408) OggS-SEEK: at 60352 want 520 got 0 (diff-requested -59832) --------------------------------------------------
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 ***