GNOME Bugzilla – Bug 470689
crash in Tasks:
Last modified: 2007-09-21 18:51:38 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 260665344 vsize: 260665344 resident: 131719168 share: 16228352 rss: 131719168 rss_rlim: 4294967295 CPU usage: start_time: 1188220676 rtime: 4627 utime: 4353 stime: 274 cutime:45 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208678688 (LWP 30652)] [New Thread -1269376112 (LWP 30743)] [New Thread -1269109872 (LWP 30701)] [New Thread -1236292720 (LWP 30693)] [New Thread -1225802864 (LWP 30687)] (no debugging symbols found) 0x003a8402 in __kernel_vsyscall ()
+ Trace 158186
Thread 1 (Thread -1208678688 (LWP 30652))
----------- .xsession-errors (85 sec old) --------------------- File "/usr/bin/puplet", line 371, in <module> main() File "/usr/bin/puplet", line 368, in main p.run() File "/usr/bin/puplet", line 355, in run self._getOnDbus() File "/usr/bin/puplet", line 229, in _getOnDbus "/Updatesd") File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 410, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230, in __init__ _dbus_bindings.UInt32(0)) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__ reply_message = self._connection.send_message_with_reply_and_block(message, timeout) dbus.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. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 467763 ***