Manuel's right, neither system-image nor u-d-m have changed since December. From comment #23 it sounds like what's changed is that the errors are now getting propagated to the ui, so they are visible to the user. @Diego: what would have happened previously, if there was an error in system-image-dbus? Would the ui have just shown no update available?
@jibel in comment #18, the checksums of the .xz files do seem to match mine. Are you saying that you've never tried to do a download on a login-protected network?
I am going to work up a branch to add some additional debug logging. I just have never seen this error on my local network. I'm still suspecting some kind of login-required issue (though I'll keep jibel's comment in mind), so I'll see if I can figure out how to mimic this behavior with a proxy, or head up to the local internet cafe to see what happens.
I also still think it's worthwhile to instrument u-d-m to watch out for login-protected networks.
Manuel's right, neither system-image nor u-d-m have changed since December. From comment #23 it sounds like what's changed is that the errors are now getting propagated to the ui, so they are visible to the user. @Diego: what would have happened previously, if there was an error in system-image-dbus? Would the ui have just shown no update available?
@jibel in comment #18, the checksums of the .xz files do seem to match mine. Are you saying that you've never tried to do a download on a login-protected network?
I am going to work up a branch to add some additional debug logging. I just have never seen this error on my local network. I'm still suspecting some kind of login-required issue (though I'll keep jibel's comment in mind), so I'll see if I can figure out how to mimic this behavior with a proxy, or head up to the local internet cafe to see what happens.
I also still think it's worthwhile to instrument u-d-m to watch out for login-protected networks.