GNOME Bugzilla – Bug 494603
crash in Panel: Logging in in the gnome ...
Last modified: 2007-11-13 08:54:54 UTC
Version: 2.18.3 What were you doing when the application crashed? Logging in in the gnome desktop Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 276656128 vsize: 276656128 resident: 40624128 share: 35098624 rss: 40624128 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194444659 rtime: 50 utime: 39 stime: 11 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496413552 (LWP 5030)] (no debugging symbols found) 0x0000003e78c0d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 176050
Thread 1 (Thread 46912496413552 (LWP 5030))
----------- .xsession-errors --------------------- localuser:backes being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/4949 Initializing nautilus-open-terminal extension ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name compiz: pixmap 0x12001a1 can't be bound to texture compiz: pixmap 0x1200207 can't be bound to texture ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-panel:5030): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffca3fd000 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 446183 ***