#5137 HIGH Update.: Watch and Listen does not release the sound device when not in focus
Zarro Boogs per Child
bugtracker at laptop.org
Thu Nov 29 19:08:28 EST 2007
#5137: Watch and Listen does not release the sound device when not in focus
-----------------------------+----------------------------------------------
Reporter: erikos | Owner: kreneskyp
Type: defect | Status: new
Priority: high | Milestone: Update.1
Component: helix-activity | Version:
Resolution: | Keywords:
Verified: 0 |
-----------------------------+----------------------------------------------
Comment(by kreneskyp):
added patch to stop the engine while inactive which releases the audio
device. This change requires that the link to the media file must be kept
alive. Currently that does not happen. This patch also uses the
datastore to retrieve the file but it introduces a new bug.
After closing watch and listen it will then crash every time it is loaded
with the following error. No other errors are seen in logs for w&l or
datastore.
1196306592.7742 ERROR - root: Traceback (most recent call last):
File "/usr/lib/python2.5/site-
packages/sugar/activity/activityfactoryservice.py", line 115, in create
activity = self._constructor(activity_handle)
File "/usr/share/activities/Watch &
Listen.activity/MediaPlayerActivity.py", line 143, in __init__
activity.Activity.__init__ (self, handle)
File "/usr/lib/python2.5/site-packages/sugar/activity/activity.py", line
285, in __init__
self._jobject = datastore.get(handle.object_id)
File "/usr/lib/python2.5/site-packages/sugar/datastore/datastore.py",
line 184, in get
metadata = dbus_helpers.get_properties(object_id)
File "/usr/lib/python2.5/site-packages/sugar/datastore/dbus_helpers.py",
line 70, in get_properties
return _get_data_store().get_properties(uid, byte_arrays=True)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 136, in
__call__
**keywords)
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 603, 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.
--
Ticket URL: <http://dev.laptop.org/ticket/5137#comment:5>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list