GNOME Bugzilla – Bug 455048
crash in Panel: User logon
Last modified: 2007-07-10 13:08:51 UTC
Version: 2.18.2 What were you doing when the application crashed? User logon 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: Bluecurve Icon Theme: Bluecurve Memory status: size: 70389760 vsize: 70389760 resident: 30826496 share: 27844608 rss: 30826496 rss_rlim: 4294967295 CPU usage: start_time: 1183961755 rtime: 30 utime: 25 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 -1208277280 (LWP 2747)] 0x0069f402 in __kernel_vsyscall ()
+ Trace 146648
Thread 1 (Thread -1208277280 (LWP 2747))
----------- .xsession-errors (7 sec old) --------------------- "/Updatesd") File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 226, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 236, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 165, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 261, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 598, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files warning: the debug information found in "/usr/lib/debug//usr/bin/gnome-panel.debug" does not match "/usr/bin/gnome-panel" (CRC mismatch). --------------------------------------------------
*** This bug has been marked as a duplicate of 446183 ***