GNOME Bugzilla – Bug 448434
crash in Panel:
Last modified: 2007-06-17 16:44:11 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: Enforcing Accessibility: Disabled GTK+ Theme: Amaranth Icon Theme: Amaranth Memory status: size: 55705600 vsize: 55705600 resident: 22990848 share: 20045824 rss: 22990848 rss_rlim: 4294967295 CPU usage: start_time: 1182072973 rtime: 19 utime: 15 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 -1208473888 (LWP 2810)] (no debugging symbols found) 0x004fb402 in __kernel_vsyscall ()
+ Trace 141611
Thread 1 (Thread -1208473888 (LWP 2810))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/equilibrium:/tmp/.ICE-unix/2689 Xgl is not running: compiz/beryl will not be launched. winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-panel:2810): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml Always: Starting Beagle Daemon (version 0.2.16.2) Always: Running on Mono 1.2.3 Always: Using sqlite version 3 Always: Command Line: /usr/lib/beagle/BeagleDaemon.exe --autostarted --bg kbuildsycoca running... --------------------------------------------------
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 ***