[Bug 1578642] Re: Xenial tasksel "manual package selection" during installation does nothing

Thomas Ward teward at trekweb.org
Thu May 5 13:41:05 UTC 2016

If "manual package selection" is no longer something we wish to support,
then perhaps it should be removed from 'tasksel'.

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to tasksel in Ubuntu.

  Xenial tasksel "manual package selection" during installation does

Status in tasksel package in Ubuntu:

Bug description:
  NOTE: This bug was filed via `ubuntu-bug` on an Ubuntu Server machine
  post-install.  The issue appeared on the Xenial ISOs, and likely still
  exists (pending a Yakkety image I can dig up which will actually
  install on a VM).

  While not part of the ISO testing, it was discovered by myself that
  the "Manual Package Selection" task no longer operates in the Ubuntu
  Server installer ISO.

  The ISO probably absorbs this error, but this error is output to the
  Terminal when you try and use "manual package selection" in tasksel

  Can't exec "/usr/lib/tasksel/packages/manual": No such file or directory at /usr/bin/tasksel line 295.
  Use of uninitialized value in split at /usr/bin/tasksel line 295.

  With 15.10 and earlier (Trusty included), this is not an issue, 'manual package selection' works in both post-installation and during the installation of the system.

  (This was tested on the Server ISOs, and with Ubuntu Server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tasksel 3.34ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May  5 09:26:43 2016
  InstallationDate: Installed on 2016-04-19 (15 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  PackageArchitecture: all
   PATH=(custom, no user)
  SourcePackage: tasksel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list