Fresh minimal desktop installation has packages pending autoremoval, pending updates

Bug #1798992 reported by Tom Reynolds
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Unassigned
Eoan
Won't Fix
High
Unassigned
Focal
Fix Released
High
Unassigned

Bug Description

Expected outcome:
After installation, no packages should pend autoremoval (they should have been apt --purge autoremove'd during the installation) and (if 'install updates during installation' option is left enabled during installation) there should be no pending updates.

Actual outcome:
Doing a 'minimal' (set of installed packages) subiquity installation of 18.10 with the (default) 'download updates while installing' option left enabled, you end up with many packages pending autoremoval, as well as pending updates. See below for apt CLI output.

To do:
Please consider reviewing / updating the test cases to improve upon this for 19.04 and later. Thank you.

---

Apt CLI output:

root@x:~# apt update
Hit:1 http://security.ubuntu.com/ubuntu cosmic-security InRelease
Hit:2 http://de.archive.ubuntu.com/ubuntu cosmic InRelease
Hit:3 http://de.archive.ubuntu.com/ubuntu cosmic-updates InRelease
Hit:4 http://de.archive.ubuntu.com/ubuntu cosmic-backports InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@x:~# apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  fonts-liberation2 fonts-opensymbol gir1.2-geocodeglib-1.0
  gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gir1.2-gudev-1.0
  gir1.2-udisks-2.0 grilo-plugins-0.3-base guile-2.2-libs
  libboost-date-time1.67.0 libboost-filesystem1.67.0 libboost-iostreams1.67.0
  libboost-locale1.67.0 libcdr-0.1-1 libclucene-contribs1v5 libclucene-core1v5
  libcmis-0.5-5v5 libcolamd2 libcurl4 libdazzle-1.0-0 libe-book-0.1-1 libeot0
  libepubgen-0.1-1 libetonyek-0.1-1 libevent-2.1-6 libexiv2-14
  libfreerdp-client2-2 libfreerdp2-2 libgc1c2 libgee-0.8-2 libgexiv2-2
  libgom-1.0-0 libgpgmepp6 libgpod-common libgpod4 liblangtag-common
  liblangtag1 liblirc-client0 liblua5.3-0 libmediaart-2.0-0 libminiupnpc17
  libmspub-0.1-1 libodfgen-0.1-1 libqqwing2v5 libraw16 librevenge-0.0-0
  libsgutils2-2 libssh-4 libsuitesparseconfig5 libvncclient1 libwinpr2-2
  libxapian30 libxmlsec1 libxmlsec1-nss lp-solve media-player-info
  python3-mako python3-markupsafe syslinux syslinux-common syslinux-legacy
  usb-creator-common
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  gnome-software gnome-software-common gnome-software-plugin-snap
  ubuntu-software
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/3.036 kB of archives.
After this operation, 3.072 B of additional disk space will be used.
Do you want to continue? [Y/n]

Related branches

Revision history for this message
Tom Reynolds (tomreyn) wrote :

See also bug 1802337

Simon Quigley (tsimonq2)
no longer affects: ubuntu-manual-tests
Revision history for this message
Tom Reynolds (tomreyn) wrote :

The reason I had filed this against ubuntu-manual-tests was that someone (I did forget who since this was back in October) asked me to file this bug exactly against his (pseudo) package.

Revision history for this message
Tom Reynolds (tomreyn) wrote :

s/asked me/recommended to/ - sorry.

Tom Reynolds (tomreyn)
affects: subiquity (Ubuntu) → ubiquity (Ubuntu)
Steve Langasek (vorlon)
Changed in ubiquity (Ubuntu):
status: New → Triaged
importance: Undecided → High
tags: added: id-5c69703c382c5e410989f269
Revision history for this message
Ricardo N Feliciano (felicianotech) wrote :

I'm not sure this is a duplicate. The other bug report only mentions a few specific packages such as lvm2 and was marked as invalid for Ubuntu 19.04 Disco.

I'm having this issue and the packages to autoremove are mostly the ones listed above.

Tom Reynolds (tomreyn)
description: updated
Revision history for this message
Tom Reynolds (tomreyn) wrote :

I agree this is a separate issue. I just did a fresh Kubuntu 19.04 amd64 UEFI installation (installer ISO downloaded on 2019-04-23) in Virtualbox, selecting the 'minimal' (set of installed packages) option and the 'install updates during installation' option set.

After installation, sudo apt update succeeded without errors and sudo apt full-upgrade reported that many packages were pending installation and many others were pending removal. See the attached output for details.

Steve Langasek (vorlon)
summary: - Fresh desktop installation has packages pending autoremoval, pending
- updates
+ Fresh minimal desktop installation has packages pending autoremoval,
+ pending updates
Tom Reynolds (tomreyn)
tags: added: disco rls-ee-incoming
tags: removed: rls-ee-incoming
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

If bug #1806204 is a duplicate, please mark as so.

Revision history for this message
Julian Andres Klode (juliank) wrote :

eoan was released, so it's wontfix for that. Looking at focal images.

Changed in ubiquity (Ubuntu Eoan):
status: Triaged → Won't Fix
Revision history for this message
Julian Andres Klode (juliank) wrote :

Reproduced in focal 20191209 kubuntu image.

Revision history for this message
Julian Andres Klode (juliank) wrote :

So what happens in that ubiquity takes the list of packages to remove (minimal-remove) from the seed, and marks them for removal; but does not remove any packages no longer needed by those. Hence, the autoremovals are correct - these packages are no longer needed.

There is a further complication, as some of the packages have maintainer scripts: The blacklist only works for packages without maintainer scripts, hence we can't simply extend the blacklist with these packages. The reason for that is simple: We avoid copying the files of these packages.

Possibly we should run apt-get autopurge after copying it all.

Revision history for this message
Julian Andres Klode (juliank) wrote :
Changed in ubiquity (Ubuntu Focal):
status: Triaged → In Progress
Changed in ubiquity (Ubuntu Focal):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 20.04.4

---------------
ubiquity (20.04.4) focal; urgency=medium

  * When removing packages, also remove automatically installed packages that
    are no longer required (LP: #1798992)

 -- Julian Andres Klode <email address hidden> Mon, 16 Dec 2019 11:41:50 +0100

Changed in ubiquity (Ubuntu Focal):
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.