Comment 28 for bug 1046563

I think we might be meant to manually launch the update manager as the first thing upon loading? I have been stumbling around trying to fix this with no luck. I think in one of the attempts, it worked after a suspend then disappeared again after a full shutdown and startup. Something overwriting the fix?