update-manager auto-opened after each apt use when security updates available

This bug was fixed in the package update-notifier - 0.78

---------------
update-notifier (0.78) karmic; urgency=low

  * src/update.c:
    - better debug output
    - add AUTOLAUNCH_MINIMAL_SECURITY_INTERVAL (LP: #369198)
  * src/update-notifier.c:
    - fix typo (#365314)
  * data/apt_check.py:
    - check for security updates in the current running
      distro release (deals with cases where people have
      two distros in their sources.list)
  * remove some debug output

 -- Michael Vogt <email address hidden> Fri, 24 Apr 2009 15:39:34 +0200

I uploaded the karmic fix as a backport to my PPA at
"deb http://ppa.launchpad.net/mvo/ubuntu jaunty main"

Accepted update-notifier into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Note that it's not apt specifically, 'dpkg -i ...' use triggers it.

What gconf innvocation is necessary to _undo_ a previous use of:

  gconftool -s --type bool /apps/update-notifier/auto_launch false

is it enough to set it to true, or does the key need to be deleted before testing.

Any testers?

Dear friends,

I've installed the jaunty-proposed version (0.76.8) and tomorrow I'll have some test results.

I think that it isn't enough to install the new package. I had to log out and log back in order to be running the new version's binary. I assume that this is because it is a daemon and the process has to be stopped and loaded again from the new binary.

Many blessings.

Dear friends,

Running apt-get update today didn't cause update-manager to launch.

When I launch it manually I see that there *are* updates; the security ones that were available yesterday and more security ones from today.

Many blessings.

Indeed, you have to restart your session after the update for it to become effective.

Michael, Matthew, is it actually intentional that it doesn't pop up automatically if security updates are available?

When non-security updates are available, Update Manager should open automatically whichever is later: (a) X days after it was last open, whether that was manually or automatically, or (b) X days after updates were installed by any apt-powered method. X should default to 7.

When security updates are available, Update Manager should open automatically whichever is later: (a) Y days after it was last open, whether that was manually or automatically, or (b) Y days after updates were installed by any apt-powered method. Y should default to 1.

So yes, it is intentional that running apt-get update shouldn't cause Update Manager to open automatically. If you run apt-get update manually, it's highly likely that you're about to install updates manually too, in which case you don't want Update Manager getting in your way.

So it seems the update was too eager and now doesn't even open any more for security updates? Reopening bug.

I removed 0.76.8 from jaunty-proposed because it seems to be a regression, and there was no followup.

I close the jaunty task of this.