GNOME Bugzilla – Bug 502037
crash in Panel:
Last modified: 2007-12-06 19:22:57 UTC
Version: 2.18.3 What were you doing when the application crashed? 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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 51609600 vsize: 51609600 resident: 26214400 share: 19374080 rss: 26214400 rss_rlim: 4294967295 CPU usage: start_time: 1196947229 rtime: 21 utime: 17 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 -1208437024 (LWP 3381)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180958
Thread 1 (Thread -1208437024 (LWP 3381))
----------- .xsession-errors --------------------- ** 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... ** (gnome-session:2730): WARNING **: Failed to establish a connection with GDM: Aucun fichier ou répertoire de ce type ** (gnome-session:2730): WARNING **: Failed to establish a connection with GDM: Aucun fichier ou répertoire de ce type ** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 502036 ***