GNOME Bugzilla – Bug 483616
crash in System Log: server rebooted, crashed...
Last modified: 2007-10-06 11:14:30 UTC
Version: 2.16.0 What were you doing when the application crashed? server rebooted, crashed again after ca 75 min. Just been internet surfing for the last errorcode regards Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.22.7-57.fc6 #1 SMP Fri Sep 21 19:26:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 609759232 vsize: 0 resident: 609759232 share: 0 rss: 515379200 rss_rlim: 0 CPU usage: start_time: 1191568094 rtime: 0 utime: 830 stime: 0 cutime:387 cstime: 0 timeout: 443 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 -1208629552 (LWP 5711)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167905
Thread 1 (Thread -1208629552 (LWP 5711))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/gw.brunnengasse7.intra:/tmp/.ICE-unix/5537 ** (eggcups:5638): WARNING **: IPP request failed with status 1030 ** (eggcups:5638): WARNING **: IPP request failed with status 1030 You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. ** (bug-buddy:5720): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 364106 ***