Public bug reported:
I recently upgraded karmic, and got a new kernel (2.6.31.15.28). I
did this via ssh, using aptitude.
The upgrade stopped to ask a question ("Menu.lst has been modified. Do
you want to keep your version or use the package maintainer's version?")
and I happened to notice that the GUI on the box being upgraded was
already requesting a reboot, despite the fact that I hadn't yet answered
the question and update-initramfs had not yet run.
Had I rebooted as requested, I certainly would not have gotten the new
kernel. And, I would have left several packages in half-installed
states.
So, the Gnome GUI applet that asks you to reboot (whatever it is) is
apparently getting notified too early in the upgrade procedure.
Normally, that doesn't matter if the installation completes rapidly, but
if it stops to ask a question, it becomes obvious. Possibly, this could
cause trouble, even under normal circumstances, if someone hits the
reboot button rapidly. It's a sort of race condition between the human
and the installation process.
My guess is that the GUI is triggered when the new kernel (the linux-
image-2.6.31.15.28 package) is installed. However, the new kernel is
not yet bootable at that point.
Also, it's generally a bad idea to reboot until the upgrade has entirely
finished. The reboot request should really be deferred to the end of
the aptitude run. (Quite likely, similar problems occur with the
Synaptic GUI tool, too...)
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: aptitude
** Tags added: aptitude
--
GUI requests a reboot too soon
https://bugs.launchpad.net/bugs/478696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
