Comment 6 for bug 370454

now that I know what this is about, I found the bug 365840 which describes exactly the same issue - a fix was found but I ran obviously my upgrade too soon, and the fixed update-manager was not pushed yet into any download