GNOME Bugzilla – Bug 452610
crash in System Log: Ik starte systeemlogbook...
Last modified: 2007-07-01 10:27:46 UTC
Version: 2.16.0 What were you doing when the application crashed? Ik starte systeemlogbook als root puur uit FC6 intresse 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.20-1.2962.fc6xen #1 SMP Tue Jun 19 19:47:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 48586752 vsize: 0 resident: 48586752 share: 0 rss: 24326144 rss_rlim: 0 CPU usage: start_time: 1183226829 rtime: 0 utime: 17 stime: 0 cutime:14 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208314160 (LWP 3730)] (no debugging symbols found) 0x00b7b402 in __kernel_vsyscall ()
+ Trace 144898
Thread 1 (Thread -1208314160 (LWP 3730))
----------- .xsession-errors --------------------- ** (eggcups:3599): WARNING **: IPP request failed with status 1030 ** (eggcups:3599): 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. ** (gnome-system-monitor:3687): WARNING **: SELinux was found but is not enabled. Loading "installonlyn" plugin ** (bug-buddy:3734): WARNING **: Kon geen pictogram laden voor Map openen --------------------------------------------------
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 ***