GNOME Bugzilla – Bug 449861
crash in Panel: I didn't know it crashed
Last modified: 2007-06-22 10:52:59 UTC
Version: 2.18.2 What were you doing when the application crashed? I didn't know it crashed Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 54415360 vsize: 54415360 resident: 27201536 share: 23523328 rss: 27201536 rss_rlim: 4294967295 CPU usage: start_time: 1182455823 rtime: 190 utime: 169 stime: 21 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 -1208338720 (LWP 5726)] (no debugging symbols found) 0x00239402 in __kernel_vsyscall ()
+ Trace 142733
Thread 1 (Thread -1208338720 (LWP 5726))
----------- .xsession-errors (20 sec old) --------------------- SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/5606 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (nautilus:5727): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-panel:5726): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** (nautilus:5727): WARNING **: Can not caclulate _NET_NUMBER_OF_DESKTOPS ** (nautilus:5727): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:5727): WARNING **: Can not get _NET_WORKAREA ** (nautilus:5727): WARNING **: Can not determine workarea, guessing at layout --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 446183 ***