GNOME Bugzilla – Bug 508509
crash in Panel: Loggin in after getting ...
Last modified: 2008-01-10 18:47:34 UTC
Version: 2.18.3 What were you doing when the application crashed? Loggin in after getting problems with panel plugins Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 63500288 vsize: 63500288 resident: 25530368 share: 22208512 rss: 25530368 rss_rlim: 4294967295 CPU usage: start_time: 1199972114 rtime: 20 utime: 16 stime: 4 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 -1208920352 (LWP 21458)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184793
Thread 1 (Thread -1208920352 (LWP 21458))
----------- .xsession-errors --------------------- [ DEBUG] Adding DataProvider Wrapper: SmugMug twoway (UID: SmugMugTwoWay-None) to TreeModel [ INFO] Restoring Sync Set [ INFO] /home/lpv/.conduit/settings-dev.xml not present [ DEBUG] DBus Exported: / [ DEBUG] DBus Exported: /syncset/gui [ DEBUG] DBus Exported: /syncset/dbus file index is too big - discontinuing index ** (trackerd:21483): WARNING **: could not open file index is too big - discontinuing index ** (trackerd:21483): WARNING **: could not open ** 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 ***