GNOME Bugzilla – Bug 472436
crash in Panel: dfds
Last modified: 2007-09-02 13:08:06 UTC
Version: 2.18.3 What were you doing when the application crashed? dfds 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 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 40161280 vsize: 40161280 resident: 21004288 share: 16953344 rss: 21004288 rss_rlim: 4294967295 CPU usage: start_time: 1188624060 rtime: 57 utime: 46 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (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 -1208506656 (LWP 2956)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 159541
Thread 1 (Thread -1208506656 (LWP 2956))
----------- .xsession-errors --------------------- Initialising tracker... throttle level is 0 seahorse nautilus module initialized Initializing nautilus-flac-converter extension 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. Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension Initializing nautilus-image-converter extension ** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... --------------------------------------------------
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 452428 ***