Git commit 4028651c70dc854965c2c994074f0798690b516d by Jonathan Thomas.
Committed on 26/09/2012 at 18:01.
Pushed by jmthomas into branch 'qapt2'.
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 4028651c70dc854 965c2c994074f07 98690b516d by Jonathan Thomas.
Committed on 26/09/2012 at 18:01.
Pushed by jmthomas into branch 'qapt2'.
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/4028651c70 dc854965c2c9940 74f0798690b516d