[Bug 1544904] Re: Updating 15.10 to 16.04 alpha2 failed: subprocess exit status 127

[Hadmut Danisch]

After adding /usr/sbin to /etc/environment, the upgrade runs smoothly.

This is weird, since /etc/environment is the common setting for all
users, and thus would not necessarily contain /usr/sbin, which contains
things for root only. It is definitely not obvious that the upgrade
process replaces the (correct and complete) PATH of the root shell with
that of /etc/environment.


regards

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1544904

Title:
  Updating 15.10 to 16.04 alpha2 failed: subprocess exit status 127

Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  just some testing feedback:

  I yesterday tried to update a Xubuntu 15.10 64bit (latest update
  status) to 16.04 alpha2 with update-manager -d, which went wrong and
  aborted (not a  problem, was just a virtual testing machine and I made
  a snapshot before upgrading, can jump back to the state before
  updating with a mouse click).

  Within the upgrade process, several packages failed and complained
  like

    got an error from dpkg for pkg: 'install-info': 'subprocess
  installed post-installation script returned an error exit status 127'

  
  Lots of these messages, also for gconf2, util-linux, initscripts, sgml-base, systemd, systemd-sysv, e2fsprogs, hostname,...

  
  Unfortunately, no further details, not even in the upgrade logs, just lots of messages like this, just with different package names.  

  
  These problems (seems to be the same problem for all) caused an avalanche of uninstallable packages due to dependencies, and finally caused update-manager to abort half-way. Especially systemd could not be properly installed. Now  I have a (more or less) running system somewhere in the middle between 15.10 and 16.04.  (I mean: Wow. Which OS would still boot and work in important aspect when stuck in the middle of an upgrade?) 

  However: As far as I can see there is a single problem causing this
  exit status 127, common in many post-installation scripts, which makes
  the upgrade process crash completely.

  regards
  --- 
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-08-28 (170 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  Package: ubuntu-release-upgrader (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial dist-upgrade
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-02-11 (3 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo video www-data
  VarLogDistupgradeTermlog:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1544904/+subscriptions