Comment 4 for bug 1217098

On Oct 25, 2013, at 07:03 AM, Didier Roche wrote:

>That doesn't sounds like a good way of designing the API. The UI
>shouldn't have to know if this errors is because the daemon timed out
>and wasn't able to restore its state or because something else on the
>system is screwed.
>
>For instance, let's imagine we want to report automatically when
>ApplyUpdate() failed (in addition to the feedback from the user). So, we
>have to take into account the case "the daemon timeouts and this is
>excepted to fail" with "there is a real issue on the system"?

Yeah, I was hoping for an easy way out, but I agree it sucks. ;)

Another possible easy way out would be to not timeout-exit when an upgrade is
fully downloaded and ready to be applied. Of course, the process could exit
for any number of reasons, but waiting to click 'Apply' will probably be the
most common reason.

I'll need to think about this more because it's going to be tough to fix.