GNOME Bugzilla – Bug 453122
crash in Panel:
Last modified: 2007-07-02 15:50:14 UTC
Version: 2.18.2 What were you doing when the application 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: Clearlooks Icon Theme: Fedora Memory status: size: 46600192 vsize: 46600192 resident: 21606400 share: 19283968 rss: 21606400 rss_rlim: 4294967295 CPU usage: start_time: 1183386825 rtime: 34 utime: 29 stime: 5 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 -1208826144 (LWP 25446)] (no debugging symbols found) 0x00886402 in __kernel_vsyscall ()
+ Trace 145266
Thread 1 (Thread -1208826144 (LWP 25446))
----------- .xsession-errors --------------------- localuser:admin being added to access control list SESSION_MANAGER=local/mega-toshiba.ur.ru:/tmp/.ICE-unix/25327 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-panel:25446): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** (gnome-panel:25446): WARNING **: panel-applet-frame.c:1283: failed to load applet OAFIID:GNOME_Panel_TrashApplet: Failed to resolve, or extend '!prefs_key=/apps/panel/applets/trash_applet/prefs;background=none:;orient=up;size=x-small;locked_down=false --------------------------------------------------
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 ***