GNOME Bugzilla – Bug 453331
crash in Panel: login in X-desktop
Last modified: 2007-07-03 12:22:30 UTC
Version: 2.18.2 What were you doing when the application crashed? login in X-desktop 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: Clearlooks Icon Theme: Fedora Memory status: size: 65974272 vsize: 65974272 resident: 21893120 share: 17817600 rss: 21893120 rss_rlim: 4294967295 CPU usage: start_time: 1183457001 rtime: 34 utime: 30 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 -1209129248 (LWP 2696)] (no debugging symbols found) 0x00f40402 in __kernel_vsyscall ()
+ Trace 145421
Thread 1 (Thread -1209129248 (LWP 2696))
----------- .xsession-errors (16 sec old) --------------------- Starting SCIM as daemon ... Launching a SCIM process with x11... Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2563 GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-panel:2696): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
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 ***