Ticket #2319 (new defect)
Opened 3 years ago
Resuming large file from external media doesn't work because of dbus timeout
|Reported by:||sascha_silbe||Owned by:||alsroot|
|Priority:||Unspecified by Maintainer||Milestone:||Unspecified by Release Team|
|Component:||journal||Version:||Git as of bugdate|
When trying to resume a large file (Journal backup bundle, ~400MB) from a mounted volume (internal hard disk), a dbus timeout happens. No user feedback is given even though the fix for #1842 has been merged.
1284311202.043779 DEBUG root: get_file asked for file with path '/media/tmp/Journal backup of SaschaSilbe (d0693262a0d0ae006cc9fedca6d8176571a0a3a9) on 12.09.2010.xmj' 1284311202.044164 DEBUG root: model.write '' '' '/media/tmp/Journal backup of SaschaSilbe (d0693262a0d0ae006cc9fedca6d8176571a0a3a9) on 12.09.2010.xmj' True Traceback (most recent call last): File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.6/site-packages/jarabe/journal/listview.py", line 528, in __icon_clicked_cb misc.resume(metadata) File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.6/site-packages/jarabe/journal/misc.py", line 213, in resume tree_id = model.copy(metadata, '/') File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.6/site-packages/jarabe/journal/model.py", line 488, in copy return write(metadata, file_path, transfer_ownership=False) File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.6/site-packages/jarabe/journal/model.py", line 505, in write file_path, transfer_ownership) File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 630, 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.
The data store call only returns after the entry has been successfully stored, so we need to increase the DBus timeout.
This happened with the version support branch, but mainline doesn't set dbus timeouts either so will have the same issue.