Git commit 6d9581b2984c89e0ed91a27a205b345e67198c01 by Jonathan Thomas.
Committed on 26/09/2012 at 18:01.
Pushed by jmthomas into branch '1.4'.
Exceptions that MetaReleaseCore throw during a download happen in a separate thread, so we can't catch them.
The root cause of the IOError seems to be the existence of a proxy, and it appears that UpdateManager has a proxy init function. (Poor design on UpdateManager's part...)
This should fix the root cause of this bug, but I fear for other exceptions that could be thrown that MetaReleaseCore won't catch for us...
I'll commit a separate fix to make our KProcess call to releasechecker non-blocking.
Git commit 6d9581b2984c89e 0ed91a27a205b34 5e67198c01 by Jonathan Thomas.
Committed on 26/09/2012 at 18:01.
Pushed by jmthomas into branch '1.4'.
Exceptions that MetaReleaseCore throw during a download happen in a separate thread, so we can't catch them.
The root cause of the IOError seems to be the existence of a proxy, and it appears that UpdateManager has a proxy init function. (Poor design on UpdateManager's part...)
This should fix the root cause of this bug, but I fear for other exceptions that could be thrown that MetaReleaseCore won't catch for us...
I'll commit a separate fix to make our KProcess call to releasechecker non-blocking.
M +11 -14 kded/distupgrad eevent/ releasechecker
http:// commits. kde.org/ muon/6d9581b298 4c89e0ed91a27a2 05b345e67198c01