GNOME Bugzilla – Bug 392565
crash in System Log: log-watch failed after g...
Last modified: 2007-01-04 01:09:53 UTC
Version: 2.16.0 What were you doing when the application crashed? log-watch failed after getting updated log-watch. Tried to re-install it to no avail. system also hungup a couple times after getting updates. 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.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2541 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 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 ** (bug-buddy:2759): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 77611008 vsize: 0 resident: 77611008 share: 0 rss: 14958592 rss_rlim: 0 CPU usage: start_time: 1167871390 rtime: 0 utime: 23 stime: 0 cutime:17 cstime: 0 timeout: 6 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 -1208428320 (LWP 2755)] (no debugging symbols found) 0x00b79402 in __kernel_vsyscall ()
+ Trace 99192
Thread 1 (Thread -1208428320 (LWP 2755))
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 374597 ***