GNOME Bugzilla – Bug 480678
crash in Panel: logging in
Last modified: 2007-10-02 19:26:03 UTC
Version: 2.18.2 What were you doing when the application crashed? logging in 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.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 36847616 vsize: 36847616 resident: 18034688 share: 15343616 rss: 18034688 rss_rlim: 4294967295 CPU usage: start_time: 1190826412 rtime: 22 utime: 19 stime: 3 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 -1208711456 (LWP 22464)] (no debugging symbols found) 0x008c7402 in __kernel_vsyscall ()
+ Trace 165708
Thread 1 (Thread -1208711456 (LWP 22464))
----------- .xsession-errors --------------------- File "/usr/bin/puplet", line 229, in _getOnDbus "/Updatesd") File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 226, in get_object (gnome-panel:22464): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 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 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!