Description Tim Petersen 2015-02-06 11:13:24 CET

Since errata 66 we introduced a regression that leads to the situation that the updater.log is not loaded and nothing happens.
This is critical as the customer:
a) doesn't recognize that there is a running update (the update runs, indeed!)
b) doesn't get any feedback if it started, when it started and more critical
c) when its finished

side note: The "back"  button is also not usable, there the umc recognizes the update ("not possible because of running update...)