Not that you care, but it's tricky to craft a test case for this because the crash doesn't actually affect any behavior! Since the UpdateDownloaded signal is emitted before the checking lock is released, everything still works. The only effect is that s-i-d tracebacks, and you only see that in the crash report because of the way dbus-python's error handling works.
This probably means that the best thing to do is just explicitly swallow any exceptions from .release(). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp