Software Updater is sometimes blank when there are ONLY phased updates and auto-removable kernels

Bug #1783023 reported by halogen2
116
This bug affects 23 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Confirmed
High
Unassigned
Xenial
Confirmed
High
Unassigned
Bionic
Confirmed
High
Unassigned
Cosmic
Won't Fix
High
Unassigned

Bug Description

Environment:

$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04

$ apt-cache policy update-manager
update-manager:
  Installed: 1:18.04.11.3
  Candidate: 1:18.04.11.3
  Version table:
 *** 1:18.04.11.3 500
        500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1:18.04.11 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

Description:

When Software Updater finds ONLY phased updates and auto-removable kernels, sometimes it comes up blank. i.e. it says "Updated software is available for this computer", but the list of available updates contains nothing. It does say the size of how much data will be downloaded. But no details of what this download is or what changes will be made if I click Install Now.

This occurred most recently on 21 July, when I had one auto-removable kernel and the following updates were available in principle -

$ apt list --upgradable
Listing... Done
libnss-systemd/bionic-updates 237-3ubuntu10.2 amd64 [upgradable from: 237-3ubuntu10]
libpam-systemd/bionic-updates 237-3ubuntu10.2 amd64 [upgradable from: 237-3ubuntu10]
libsystemd0/bionic-updates 237-3ubuntu10.2 amd64 [upgradable from: 237-3ubuntu10]
libudev1/bionic-updates 237-3ubuntu10.2 amd64 [upgradable from: 237-3ubuntu10]
systemd/bionic-updates 237-3ubuntu10.2 amd64 [upgradable from: 237-3ubuntu10]
systemd-sysv/bionic-updates 237-3ubuntu10.2 amd64 [upgradable from: 237-3ubuntu10]
udev/bionic-updates 237-3ubuntu10.2 amd64 [upgradable from: 237-3ubuntu10]

Expected results:

Depending on whether I "should" receive the avilable phased updates or not, I would have expected that...

A) ... if I should have received some of the available phased updates, Software Updater should present them to me, and offer to remove the auto-removable kernels.

B) ... if I should not receive any of the available phased updates yet, Software Updater should either
  i) only offer to remove the auto-removable kernels, OR
  ii) just say "The software on this computer is up to date."

ubuntuforums thread (which includes a screenshot):
https://ubuntuforums.org/showthread.php?t=2394240

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for taking your time to report this issue and help making Ubuntu better.

I've seen the same behaviour on my 18.04 system. It didn't use to show the update-manager window in older releases when only phased updates were available so it might be the removable kernels which are triggering it. (Or a combination of the two?)

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. This will automatically add version numbers and other relevant information. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in update-manager (Ubuntu):
status: New → Confirmed
tags: added: bionic
Revision history for this message
Brian Murray (brian-murray) wrote :

This happened to an Ubuntu user I know here is a photo of what they saw in the terminal on July 20, 2018.

Changed in update-manager (Ubuntu):
importance: Undecided → High
tags: added: rls-cc-incoming
Changed in update-manager (Ubuntu Bionic):
importance: Undecided → High
tags: removed: rls-cc-incoming
Revision history for this message
Balint Reczey (rbalint) wrote :

Phased updates were not considered when kernel removal was added, we need to check for them, too.

Autoremoval is expected to be offered when there are installable packages, but phased packages are not always installable.

tags: added: id-5b59f775168877b93e7f264b
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-manager (Ubuntu Bionic):
status: New → Confirmed
Revision history for this message
William Tobin (william-tobin) wrote :

I'm running 16.04 LTS, and this bug has appeared in the last month or so.
I initially wondered if a phisher was wanting me to download some virus since there no details of the upgrades were displayed. Because the size of the upgrades increased over time, I presumed not and decided to "Install Now".

Changed in update-manager (Ubuntu Xenial):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Tammara Garland (1palmtree) wrote :

Discovered today that the thread I posted to on prior days was a duplicate to this thread, so now I'm updating here. This bug with my system first appeared August 9th. Yesterday I decided to go ahead and install whatever updates were there (even though I could not see 'what' the updates were since the box was blank). This was what occurred yesterday with my system while running the updater:

16.04.5 LTS xenial

The 'software updater' continued to show only the blank white box, but indicated there was updates to install. I decided to go ahead and run it through the installation process. (See attached image).

With the plain white box there was no way to see 'what' the updates would be. But, after selecting 'install', the Terminal Emulator opened and showed the installation progress as it normally does.

When the update was complete the message, "The Software on This Computer is Up to Date" also came up as normal. So the only bug appears to be just the blank white box not revealing 'what' the updates are.

Now for today: I just ran the Software Updater and it is now functioning properly - showing what the available updates are in the box as it should - not just a blank white box as before, so for me it seems to have been resolved - at least for now! Thanks!

Revision history for this message
Mikkel Kirkgaard Nielsen (mikini) wrote :
Download full text (6.5 KiB)

Seeing the same behaviour on this 16.04 system:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial

$ apt-cache policy update-manager
update-manager:
  Installed: 1:16.04.13
  Candidate: 1:16.04.13
  Version table:
 *** 1:16.04.13 500
        500 http://dk.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        500 http://dk.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1:16.04.12 500
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages
     1:16.04.3 500
        500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        500 http://dk.archive.ubuntu.com/ubuntu xenial/main i386 Packages

$ apt list --upgradeable
Listing... Done
chromium-browser/xenial-updates,xenial-security 68.0.3440.106-0ubuntu0.16.04.1 amd64 [upgradable from: 68.0.3440.75-0ubuntu0.16.04.1]
chromium-browser-l10n/xenial-updates,xenial-updates,xenial-security,xenial-security 68.0.3440.106-0ubuntu0.16.04.1 all [upgradable from: 68.0.3440.75-0ubuntu0.16.04.1]
chromium-codecs-ffmpeg-extra/xenial-updates,xenial-security 68.0.3440.106-0ubuntu0.16.04.1 amd64 [upgradable from: 68.0.3440.75-0ubuntu0.16.04.1]
flashplugin-installer/xenial-updates,xenial-security 30.0.0.154ubuntu0.16.04.1 amd64 [upgradable from: 30.0.0.134ubuntu0.16.04.1]
gir1.2-javascriptcoregtk-4.0/xenial-updates,xenial-security 2.20.5-0ubuntu0.16.04.1 amd64 [upgradable from: 2.20.3-0ubuntu0.16.04.1]
gir1.2-webkit2-4.0/xenial-updates,xenial-security 2.20.5-0ubuntu0.16.04.1 amd64 [upgradable from: 2.20.3-0ubuntu0.16.04.1]
josm/unknown,unknown 1.5.svn14163 all [upgradable from: 1.5.svn14066]
libapache2-mod-php/xenial,xenial 1:7.2+62+ubuntu16.04.1+deb.sury.org+3 all [upgradable from: 1:7.2+62+ubuntu16.04.1+deb.sury.org+1]
libapache2-mod-php7.2/xenial 7.2.9-1+ubuntu16.04.1+deb.sury.org+1 amd64 [upgradable from: 7.2.8-1+ubuntu16.04.1+deb.sury.org+1]
libjavascriptcoregtk-4.0-18/xenial-updates,xenial-security 2.20.5-0ubuntu0.16.04.1 amd64 [upgradable from: 2.20.3-0ubuntu0.16.04.1]
libjavascriptcoregtk-4.0-dev/xenial-updates,xenial-security 2.20.5-0ubuntu0.16.04.1 amd64 [upgradable from: 2.20.3-0ubuntu0.16.04.1]
libnss-myhostname/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2]
libpam-systemd/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2]
libpq5/xenial-updates,xenial-security 9.5.14-0ubuntu0.16.04 amd64 [upgradable from: 9.5.13-0ubuntu0.16.04]
libsystemd-dev/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2]
libsystemd0/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2]
libudev-dev/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2]
libudev1/xenial-updates 229-4ubuntu21.4 amd64 [upgradable from: 229-4ubuntu21.2]
libwebkit2gtk-4.0-37/xenial-updates,xenial-security 2.20.5-0ubuntu0.16.04.1 amd64 [upgradable from: 2.20.3-0ubuntu0.16.04.1]
libwebkit2gtk-4.0-37-gtk2/xenial-updates,xenial-security 2.20.5-0ubuntu0.16.04.1 amd64 [upgradable from: 2.20.3-0ub...

Read more...

Revision history for this message
Mikkel Kirkgaard Nielsen (mikini) wrote :

Still seeing this (haven't updated, neither using apt nor update-manager because this bug annoys me).

Digged for when this was introduced in update-manager and found the package was updated in June:

$ zgrep update-manager /var/log/apt/hi*2* -B3 -A1
/var/log/apt/history.log.2.gz:Start-Date: 2018-06-26 13:34:44
/var/log/apt/history.log.2.gz:Commandline: apt upgrade
/var/log/apt/history.log.2.gz:Requested-By: miki (1000)
/var/log/apt/history.log.2.gz:Upgrade: update-manager-core:amd64 (1:16.04.12, 1:16.04.13), unity-control-center-faces:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), update-manager:amd64 (1:16.04.12, 1:16.04.13), gnome-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), virtualbox-dkms:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2), virtualbox:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2), unity-control-center:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), ubuntu-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:amd64 (1:16.04.12, 1:16.04.13), libunity-control-center1:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), virtualbox-qt:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2), gnome-software-common:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11)
/var/log/apt/history.log.2.gz:End-Date: 2018-06-26 13:36:58

Seems like the bug is introduced in 1:16.04.13: https://launchpad.net/ubuntu/+source/update-manager/1:16.04.13

Full patch here: https://launchpadlibrarian.net/370576411/update-manager_1%3A16.04.12_1%3A16.04.13.diff.gz

Though, looking through the path I can't identify any connection with phased updates. The changes seems to relate to autoremoving only.

Balint Reczey (rbalint)
Changed in update-manager (Ubuntu Cosmic):
status: Confirmed → In Progress
assignee: nobody → Balint Reczey (rbalint)
Revision history for this message
hbchoong (hbchoong) wrote :

Unfortunately still affecting 18.04.1 LTS, observed on and off again using Software Updater.
Recent system update performed 16/Dec/2018 comes up blank again, where it says "Updated software is available for this computer", but the list of available updates contains nothing. It does say the size of how much data will be downloaded. But no details of what this download is or what changes will be made if I click 'Install Now'.

FYI this is not an exact duplicate of bug #1072136 though...

Will this be addressed for Bionic in the near future? Many thanks

Revision history for this message
hbchoong (hbchoong) wrote :

Still occurring intermittently - please advise if this will be addressed in future updates?
Thanks.
NB: This is a different issue from bug #1072136

Balint Reczey (rbalint)
Changed in update-manager (Ubuntu Cosmic):
status: In Progress → Confirmed
Changed in update-manager (Ubuntu):
status: In Progress → Confirmed
assignee: Balint Reczey (rbalint) → nobody
Changed in update-manager (Ubuntu Cosmic):
assignee: Balint Reczey (rbalint) → nobody
Revision history for this message
Brian Murray (brian-murray) wrote :

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release.

Changed in update-manager (Ubuntu Cosmic):
status: Confirmed → Won't Fix
Revision history for this message
bushido (olav-magi) wrote :

I am having this bug on Ubuntu 24.04 LTS.

Revision history for this message
Nathan Teodosio (nteodosio) wrote :

Bushido, can you please add your 'apt list --upgradable -a'? I'm trying to reproduce this in 24.04 but update-manager is working correctly saying the system is up to date, although openssh-client is phasing:

% apt list --upgradable -a
openssh-client/noble-updates,noble-proposed 1:9.6p1-3ubuntu13.7 amd64 [aktualisierbar von: 1:9.6p1-3ubuntu13.5]
openssh-client/now 1:9.6p1-3ubuntu13.5 amd64 [Installiert,aktualisierbar auf: 1:9.6p1-3ubuntu13.7]
openssh-client/noble-security 1:9.6p1-3ubuntu13.4 amd64
openssh-client/noble 1:9.6p1-3ubuntu13 amd64

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.