openmoko-panel-plugin: patch and bug
arne anka
openmoko at ginguppin.de
Sun Nov 2 12:33:55 CET 2008
after a few minutes the polling of at least the battery state stops --
little investigation shows an exception, because the dbusgsmstate dict
seems not to contain the key "registration"
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
self.run()
File "/usr/lib/python2.5/threading.py", line 446, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/bin/openmoko-panel-plugin", line 660, in update_status
if self.dbusgsmstate[u'registration'] == "home":
KeyError: u'registration'
--- oldStuff/openmoko-panel-plugin 2008-10-25 23:11:43.000000000 +0200
+++ /usr/bin/openmoko-panel-plugin 2008-11-02 12:23:07.000000000 +0100
@@ -650,7 +650,7 @@
try:
self.dbusgsmstate =
Interface(self.resources_proxy["GSMVALS"],
"org.freesmartphone.GSM.Network").GetStatus()
except:
- self.dbusgsmstate = {}
+ self.dbusgsmstate = {u'registration':'n/a'}
try:
self.brightness =
dbus_object.device_display_iface.GetBrightness();
additionally, starting/stopping opp a few times seems to mess up the
frameworkd -- opp doesn't start anymore.
i've seen that several times, the most recent exception is:
Traceback (most recent call last):
File "/usr/bin/openmoko-panel-plugin", line 895, in <module>
icon = OpenmokoPanelPlugin()
File "/usr/bin/openmoko-panel-plugin", line 490, in __init__
self.dbusgsmstate = Interface(self.resources_proxy["GSMVALS"],
"org.freesmartphone.GSM.Network").GetStatus()
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 68, in
__call__
return self._proxy_method(*args, **keywords)
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in
__call__
**keywords)
File "/var/lib/python-support/python2.5/dbus/connection.py", line 622,
in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
maybe shutdown (even by kill -15 ...) should clean up better?
or is it a frameworkd issue?
More information about the community
mailing list