Red Hat Bugzilla – Bug 460598
Services unknown traceback during startup
Last modified: 2008-09-12 11:41:49 EDT
With s-c-s 0.99.22, I see lots of errors like:
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 214, in maybe_handle_message
File "/usr/lib/python2.5/site-packages/scservices/dbus/proxy/serviceherders.py", line 126, in notify
self.dbus_notify (subscriber, service_name, change)
File "/usr/lib/python2.5/site-packages/scservices/dbus/proxy/serviceherders.py", line 93, in dbus_notify
service = self.services[service_name]
The ui comes up, but the list of services remains insensitive, so it is pretty useless.
Not really a dbus communication problem, rather a "message about service status change arriving before message about service being added" one. Can I expect DBus signals to be received in the order they were sent?
*** Bug 461210 has been marked as a duplicate of this bug. ***
Created attachment 316225 [details]
Here is a (possibly useless) screenshot of the non-active list in the program.
It turned out to be a different problem. I've just implemented a fix upstream, so the next version available shouldn't show this problem anymore.
Fixed in version 0.99.23 which should hit Rawhide shortly.