Doesn't auto open update-manager as it should

Bug #1702724 reported by Sebastien Bacher
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Fix Released
High
Unassigned
Xenial
Fix Released
Undecided
Unassigned

Bug Description

* Impact

Since Xenial it seems that update-manager is not presented to users as often as it should.

* Test case

Use xenial for a week, update-manager should auto open to show you pending updates

* Regression potential

The UI might be displayed more often than it used to be

-------------------------

One possible reason is that update-notifier is trying to be too smart about when it should open the updater and reset the counter when the dpkg/apt logs timestamps change. The logic behind that was to try to not bother command line users and don't present them the graphical UI if they are doing their update using apt directly. That's not very obvious how it's working though and not playing well with unattended-upgrades (security updates get installed in background, the system thinks it's users doing their updates manually and is never prompting as a result).

The suggested fix is to just drop that smart behaviour and prompt users after the configured delay. Command line users who don't like that can just change the setting to "never"

Changed in update-notifier (Ubuntu):
importance: Undecided → High
Changed in update-notifier (Ubuntu):
status: New → In Progress
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

I thought unattended-upgrades now installs ALL updates, not only security ones, as a fix for LP: #1624641. I have not still verified that. I could be wrong.

Revision history for this message
Sebastien Bacher (seb128) wrote :

> I thought unattended-upgrades now installs ALL updates, not only security ones, as a fix for LP: #1624641.

No, that's not what the bug you pointed is about, the change was to enable the standard pocket so new depends could be installed from the archive, see http://launchpadlibrarian.net/292672379/unattended-upgrades_0.92ubuntu1_0.92ubuntu1.1.diff.gz

the updates/proposed lines are still commented and that's also the case in the current artful version

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
update-notifier (3.183) artful; urgency=medium

  * Clear out the autotools changes from the previous upload which were
    due to a miss-uses of the vcs, fixes the buid.

 -- Sebastien Bacher <email address hidden> Mon, 10 Jul 2017 13:20:35 +0200

Changed in update-notifier (Ubuntu):
status: In Progress → Fix Released
description: updated
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Sebastien, or anyone else affected,

Accepted update-notifier into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-notifier/3.168.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in update-notifier (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed verification-needed-xenial
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

SRU verification for Xenial:
I have reproduced the problem with update-notifier 3.168.5 in xenial-updates and have verified that the version of update-notifier 3.168.6 in -proposed fixes the issue.

I've set /apps/update-manager/launch-time to a timestamps in the past (< now - auto-launch-interval) and tried 2 cases:
- Fresh boot
- Refresh of the packages cache

In both cases update-manager showed up.

I also verified that the notification is not triggered when if should not (auto-launch-interval is not reached)

Marking as verification-done

tags: added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

I have rebuilt update-notifier in the security ppa so that it can be also released in the -security pocket, and got it pocket-copied into xenial-proposed. The new version number is (3.168.7).

Once this version has been tested and is ready to be release, please also copy it into xenial-security. Thanks!

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I have verified update-notifier 3.168.7 from the proposed pocket. The tests are successful and the results the same as my previous comment.

verification-done.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
update-notifier (3.168.7) xenial-security; urgency=medium

  * Rebuild in -security pocket.

 -- Marc Deslauriers <email address hidden> Thu, 18 Jan 2018 07:19:47 -0500

Changed in update-notifier (Ubuntu Xenial):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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