GNOME Bugzilla – Bug 502921
crash in Panel: Switching user
Last modified: 2007-12-12 13:11:47 UTC
Version: 2.18.0 What were you doing when the application crashed? Switching user 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: 35483648 vsize: 35483648 resident: 11456512 share: 8519680 rss: 11456512 rss_rlim: 4294967295 CPU usage: start_time: 1197320242 rtime: 22 utime: 20 stime: 2 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 -1208613152 (LWP 13621)] (no debugging symbols found) 0x009e3402 in __kernel_vsyscall ()
+ Trace 181484
Thread 1 (Thread -1208613152 (LWP 13621))
----------- .xsession-errors (7 sec old) --------------------- localuser:Jack being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/13507 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** 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 ***