[FSO] Problem suspending with frameworkd rule

Michael 'Mickey' Lauer mickey at openmoko.org
Fri Nov 7 10:39:04 CET 2008


Am Tuesday 04 November 2008 21:26:48 schrieb digger vermont:
> Hello,
>
> (Can't figure out if this is better in OM-Community or
> Smartphones-Userland)
>
> I  could use some help.  I'm have a problem with suspending an om-gta02
> using an oevent rule.  What happens is that it hangs for about a minute
> and then suspends.  The traceback is further down.
>
> The same script does works fine from a ssh, python shell, or a desktop
> icon.  I'm using fso-testing.
>
> The rule:
> -----------------------------------------------
> trigger: InputEvent()
>     filters:
>              - HasAttr(switch, "AUX")
>              - HasAttr(event, "pressed")
>     actions: Command("/usr/bin/suspend.py")
> ------------------------------------------------
>
> The test script with logging removed:
> ------------------------------------------------
> #!/usr/bin/env python
>
> import dbus
>
> def suspend():
>     bus = dbus.SystemBus()
>     service = 'org.freesmartphone.ousaged'
>     obj = '/org/freesmartphone/Usage'
>     suspend_obj = bus.get_object(service, obj)
>     suspend_obj.Suspend()
>
> if __name__ == "__main__":
>     suspend()
> ---------------------------------------------------
>
> The traceback:
> ----------------------------------------------------
> Traceback (most recent call last):
>   File "/usr/bin/suspend.py", line 30, in suspend
>     suspend_obj.Suspend()
>   File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 68, in
> __call__
>     return self._proxy_method(*args, **keywords)
>   File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in
> __call__
>     **keywords)
>   File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 622,
> in call_blocking
>     message, timeout)
> 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.
> ---------------------------------------------------------------------------
>--------
>
> I can't figure what else to try, so suggestions or hints are welcome.

Atm. we're only calling the Suspend() method from within the rules which calls 
this asynchronously and discards the result. We need to discuss the proper 
semantics for Suspend() returning when and how. Could you open a ticket?

-- 
:M:



More information about the devel mailing list