can't do dist-upgrade due to systemd

Bug #1326412 reported by Tampah Mbois
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

the problem with /var/lib/dpkg/info/libpam-systemd:i386.prerm script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't exist) and not /etc/init/systemd-logind.conf (does exist).
?

Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
  libpam-systemd
1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
3 not fully installed or removed.
Need to get 0 B/25.2 kB of archives.
After this operation, 1024 B of additional disk space will be used.
(Reading database ... 113986 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: warning: subprocess old pre-removal script returned error exit status 100
dpkg: trying script from the new package instead ...
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error processing archive /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
 subprocess new pre-removal script returned error exit status 100
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
 /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.2
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Wed Jun 4 10:51:24 2014
InstallationDate: Installed on 2014-06-02 (2 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Tampah Mbois (t4mp4h-3) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Dimitri John Ledkov (xnox) wrote : Re: can't do dist-upgrade

systemd is not yet support in ubuntu, whilst there is active ongoing work to make it on-par with upstart integration in Ubuntu.
and specifically, one cannot yet install/upgrade/configure a lot of packages if booted with systemd-init. This is a known issue and we are working on resolving it.

Upgrading trusty, and upgrading to subsequent releases will at the moment require booting under upstart.

tags: added: systemd-boot
summary: - can't do dist-upgrade
+ can't do dist-upgrade due to systemd
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

This is fixed in utopic, and will not be fixed in trusty. One will have to boot under upstart to dist-upgrade reliable within trusty, or to dist-upgrade to utopic.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → 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.