Comment 12 for bug 107249

Over the weekend some process caused me to need to reboot the machine - which is a problem because the machine "doesn't have a valid boot signature" as of the last kernel update. This is the third time a failed semi-automatic kernel update has left the computer unusable (I typically accept kernel updates because I'm hoping one of them will address one of the many USB/scanner problems). Perhaps the update-manager should confirm the update could be completed before actually writing to the drive? I am now in the same situation I was in on April 17th (can't boot) ... please let me know if there are any other log files I should attempt to pick up before I re-install with Gutsy.