I can reproduce this problem with Ubuntu 14.04 as guest and Fedora 22 as host.
The problem occurs 100% of the time with the script below.
The relevant error is:
INFO: apt-get -yf install
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies... Done
The following extra packages will be installed:
libpam-systemd
The following packages will be upgraded:
libpam-systemd
1 upgraded, 0 newly installed, 0 to remove and 55 not upgraded.
82 not fully installed or removed.
Need to get 0 B/25.5 kB of archives.
After this operation, 1024 B of additional disk space will be used.
(Reading database ... 54203 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_204-5ubuntu20.13_amd64.deb ...
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
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 ...
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error processing archive
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.13_amd64.deb (--unpack):
subprocess new pre-removal script returned error exit status 100
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart: Connection refused
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.13_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Script:
cat > script.sh <<EOF
#!/bin/bash
echo "root:root" | chpasswd
export DEBIAN_FRONTEND=noninteractive
echo "INFO: apt-get update"
apt-get update
echo "INFO: apt-get -yf upgrade"
apt-get -yf upgrade
echo "INFO: apt-get -yf install"
apt-get -yf install
echo "INFO: apt-get -y install gcc"
apt-get -y install gcc
echo "INFO: apt-get -yf install"
apt-get -yf install
echo "INFO: apt-get -y install gcc"
apt-get -y install gcc
echo "INFO: end of script (also returncode 0)"
EOF
virt-builder -x -v ubuntu-14.04 --arch x86_64 \
-o ubuntu.img \
--format qcow2 \
--run script.sh 2>&1 | tee output.txt
virt-cat -a ubuntu.img /tmp/builder.log > builder.log
** Attachment added: "Content of /tmp/builder.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+attachment/4472346/+files/builder.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1325142
Title:
failure to update libpam-systemd in 14.04 due to missing logind init
script
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Trusty:
Triaged
Status in systemd source package in Utopic:
Fix Released
Bug description:
Hi,
while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
state. 'apt-get -f install' from within the chroot will not fix it,
but if the build is made bootable and put into a iso/VM you can
recover that way in a live session.
the problem seems to be the /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)
Our build logs available upon request, but the scripts to setup the chroot to
recreate it are here:
https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh
https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh
In a web-search I notice a few others running into the same bug,
chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28
/%23ubuntu-devel.txt
someone else's build log:
https://launchpad.net/~qutim/+archive/qutim/+build/6039800
launchpad bug #1323575 seems to be a duplicate of this one.
perhaps related to older launchpad bug #1305395 ?
note we are also suffering from a failure with update-initramfs, not sure of
the root cause of that one but I thought I'd mention it in case they were
related, since they both started happening about the same time, a couple weeks
ago. (launchpad bug #1317602)
It all worked ok after the inital releases of 14.04, so something to do with
a package update since then.
thanks,
Hamish
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
