Ubuntu
update-notifier package

"restart required" notification should be delayed until the upgrade process is complete

Bug #30759 reported by Chris Moore
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Fix Released
Medium
Michael Vogt

Bug Description

I just applied a bunch of updates using "sudo apt-get dist-upgrade". The end of the output looked like this:

Setting up libdbus-1-2 (0.60-2ubuntu12) ...

Setting up libdbus-glib-1-2 (0.60-2ubuntu12) ...

Setting up libdbus-1-dev (0.60-2ubuntu12) ...
Setting up libdbus-glib-1-dev (0.60-2ubuntu12) ...
Setting up dbus (0.60-2ubuntu12) ...

Setting up dbus-1-utils (0.60-2ubuntu12) ...
Setting up powermanagement-interface (0.3.9) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend is incompatible with emacs shell buffers)
debconf: falling back to frontend: Readline

Setting up gnome-power-manager (0.3.4-0ubuntu6) ...

Setting up python2.4-dbus (0.60-2ubuntu12) ...

Something in there popped up the "restart required" bubble, while the update was still running. I left it to complete, but suspect that if I had clicked the restart icon as requested, the system may have rebooted part-way through the update.

Would it be better to hold off with the "reboot required" bubble until the update has completed?

Sebastien Bacher (seb128)
Changed in update-notifier:
assignee: nobody → mvo
Revision history for this message
Kristoffer Lundén (kristoffer-lunden) wrote :

Confirmed, happened to me too, although I didn't check what packages might have caused it.

Also agree that it should wait until all is finished.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

This is a update-notifier problem that will (hopefully) be fixed soon.

Cheers,
 Michael

Changed in update-notifier:
status: Unconfirmed → Confirmed
Revision history for this message
Chris Moore (dooglus) wrote : screenshot

This shows bugs 30759 and 30812 both at the same time.

Revision history for this message
Chris Moore (dooglus) wrote : version 0.41.5 didn't fix the problem

The changelog says:

update-notifier (0.41.5) dapper; urgency=low

    - ensure that the "reboot required" does not come up in the middle
      of the installation/update

However, as the attached screenshot shows, the bubble still comes up in the middle of the installation.

The installation was stuck at a question new kernels always ask me about lilo.conf.

After answering "no", the installation proceeded as follows:

* Wipe out your old LILO configuration and make a new one? [No] no
*
* Setting up python2.4-syck (0.55-3ubuntu2) ...
* Setting up python-syck (0.55-3ubuntu2) ...

So it wasn't finished at all. I rebooted after installing the latest update-notifier, so I'm sure it's the new version that I'm running.

Revision history for this message
Michael Vogt (mvo) wrote : Re: "restart required" bubble appeared while updates were still applying

Thanks.

Questions on the terminal are a bit of a special case. I'll look into it.

Does it behave correctly under "normal" (no questions) situations?

Thanks,
 Michael

Revision history for this message
Chris Moore (dooglus) wrote : Re: "restart required" bubble appeared when questions are asked during upgrade

I'll let you know next time I see some updates.

I don't know when that will be, because a recent update to dapper broke my network connection. I no longer have an 'eth0' interface, so for now I'm back in breezy.

It happened immediately after installing udev 079-0ubuntu9 - but this belongs in a separate bug report.

Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

I had it appear today during an upgrade when no questions were asked.

Revision history for this message
Matt Zimmerman (mdz) wrote :

If I understand the comments correctly, this will only happen in unusual circumstances, and therefore the dapper-targeted portion of this is satisfactory

Revision history for this message
Michael Vogt (mvo) wrote :

This problem was fixed a while ago. Reboot notifications are only shown when apt is finished and has written a "stamp file" that indicates that it really has finished.

Please reopen if you can reproduce the problem (with either notifications or reboot notifications) on a current dapper system.

Thanks,
 Michael

Changed in update-notifier:
status: Confirmed → Fix Released
Revision history for this message
Leonid Evdokimov (darkk) wrote :

I have reproduced the bug while upgrading karmic koala from 9.10-just-from-dvd to 9.10-up-to-date today morning.

Here is full story including happy-end: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/450620/comments/18

I have full apt logs and other logs that were not rotated still. I can upload if you need any of them.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.