GNOME Bugzilla – Bug 507038
crash in Panel: ds wa
Last modified: 2008-01-08 21:45:12 UTC
Version: 2.18.0 What were you doing when the application crashed? ds wa Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 43900928 vsize: 43900928 resident: 14163968 share: 10203136 rss: 14163968 rss_rlim: 4294967295 CPU usage: start_time: 315853531 rtime: 227 utime: 205 stime: 22 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 -1208498464 (LWP 2614)] (no debugging symbols found) 0x0074b402 in __kernel_vsyscall ()
+ Trace 183922
Thread 1 (Thread -1208498464 (LWP 2614))
----------- .xsession-errors (48 sec old) --------------------- ** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... ** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... ** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... Cannot access memory at address 0xbfafeaf8 /usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file: Couldn't get registers: No such process. Quitting: ptrace: No such process. ** 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 ***