It is longstanding practice, predating either upstart or systemd, that
users of Debian and Ubuntu systems should create a /usr/sbin/policy-rc.d
as part of their chroot setup. It is not a bug in the libpam-systemd
package that it tries to start and stop its service using the policy-
declared
Hi there!
Frankly, this issue requires some love. I hit it 10 different ways on a
ridiculous variety of setups. And as many people pointed, we're talking
about LTS here.
Could we just change the postinst script to something like this, and
declare this issue over?
# Automatically added by
I am reopening the Trusty task, as I've re-confirmed this bug in 14.04
chroot. apt upgrading will fail on libpam-systemd:
root@x250:/# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following
I confirm that this is still an issue in Trusty. However, in #1326412,
Dimitri John Ledkov 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.
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
This is very clearly not fixed on Ubuntu trusty, and the changelog of
the package in trusty does not indicate any fix was applied.
Please remove the incorrect designation of "Fix Committed" for trusty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I'm also being bitten by this issue. I can't create chroots or VM images
based on trusty due to polkit-1 bringing in libpam-systemd, which breaks
as other commenters have described earlier...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Tried today on ubuntu 14.04 LTS as host for Ubuntu 14.04 LTS under LXC
the issue still occurs with libpam-systemd amd64 204-5ubuntu20.15
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Managed to do a workaroud as suggested by Bill Gatliff (bgat) in #38.
git clone https://github.com/fgrehm/vagrant-lxc-base-boxes
edit
https://github.com/fgrehm/vagrant-lxc-base-boxes/blob/master/debian/install-extras.sh
in line 17 change PACAKGES to
vim curl wget man-db bash-completion
** Changed in: systemd (Ubuntu Trusty)
Status: Triaged => Fix Released
--
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
Has anyone made a shell script to fix this? I'm running on Android and
it's a little difficult for me to follow how to fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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...
Set root password of your VM to root:
virt-customize -a ubuntu.img --root-password "password:root"
--
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
** Attachment added: "Output (+debug output) of virt-builder"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+attachment/4472347/+files/output.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
This one-liner fails as well:
virt-builder -v -x ubuntu-14.04 -o output --root-password
"password:root" --update
--
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
Hi, also same here, as here #1326412
I can remove it with dpkg -r --force-depends but then the package
management is broken. When I reinstall it, the same error comes out:
*
# apt-get --reinstall install libpam-systemd
Reading package lists...
Building dependency tree...
Reading state
Hi, also same here, as here #1326412
I can remove it with dpkg -r --force-depends but then the package
management is broken. When I reinstall it, the same error comes out:
*
# apt-get --reinstall install libpam-systemd
Reading package lists...
Building dependency tree...
Reading state
ok looking at https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1326412
The package is not supported in Trusty?
I can't seem to even remove it, it fails with the same error.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi I am trying to build KDE packages for Kubuntu in Trusty and I now
have a broken chroot.
scarlett@scarlett-lappy:~/Work/src/4.14.3/artikulate/artikulate-4.14.3$ sudo
/usr/lib/pbuilder/pbuilder-satisfydepends
sudo: unable to resolve host scarlett-lappy
[sudo] password for scarlett:
-
This bug's over a year old for Trusty and I just encountered it again.
--
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
This thread recommends installing Debian :D
http://www.linuxforums.org/forum/ubuntu-linux/204157-libpam-systemd-
dependency-error-unable-install-any-packages-anymo.html
I don't even know whether I can safely restart my computer in this
state. Also, 14.04 LTS DOES NOT HAVE systemd. Where did you
Can you explain how you can fuck up an LTS release upgrade (not even a
major upgrade)? If you just had *one* test system running, you would
have been able to reproduce this. Amateurs...
apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
#38 Thanks, Solved it.
This problem is solved :)
Errors were encountered while processing:
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.10_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
--
You received this bug notification because you are a member of Ubuntu
Touch
Sorry I'm late to the party, but what about this as a workaround?
# dpkg-divert --local --add /etc/init.d/systemd-logind
# ln -s /bin/true /etc/init.d/systemd-logind
In the chroot, obviously. :-)
It's working for me, anyway. I did the same thing with /sbin/initctl,
per Bug #430224.
--
You
As an additional note to #35
This error only happens when I do a dist-upgrade.
I can install software and upgrade and everything seems to run smooth.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
See Bug #1359740
--
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
@Jox
I am trying your solution in #18 with UCK. It allows me to upgrade as
well as dist-upgrade and install my files, but once my .iso is made and
I try to install it under a virtualbox, it sents me to a busybox shell
instead of prompting me to install/try ubuntu.
To apply your solution I opened
very bad experience. ubuntu server 14.04 64bit, trying to fresh install
on some older DELL machine (poweredge 1950) with software raid with
separate /boot, swap and /tmp. everything seems to run ok, and after
reboot, grub works ok (except that one has to make fast boot = 0,
otherwise error
E: Sub-process /usr/bin/dpkg returned an error code (1)
(hmmm, no way to edit comments? That's not good for me)
--
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
@wlraider70
This seems not to be directly related. Same as #16 by @Michael
Heuberger.
The issue of this thread is about this message:
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind.
It can not find the initscript and thus is not able to execute it.
Whereas your message...
Similar to #11, I was getting this error trying to install on Android,
though I'm using merged (bind) mounts instead of chroot. The solution in
#3 worked for me. The problem seems to be that the /var/lib/dpkg/info
/libpam-systemd:armhf.postinst script is checking for /etc/init.d
/systemd-logind
@wlraider70
What's your exact error message?
Do you have any output if you execute 'initctl show-config' in a
terminal?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I have this issue on my current ubuntu 14.04. Is there a simple way to
fix it. I see the fix, but It seems to be for someone making a live
disk. Its a bit over my head.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Hi Paul,
thanks for the details.
I meant the result of initctl show-config in the running Ubuntu booted
from the remastered image. At the time when you get the crash report.
Not in the chroot env.
The output you get in the chroot env (no value) is expected, since
initctl is deactivated in that
@Paul:
Additionally you can run:
ls -l /sbin/initctl /usr/sbin/update-grub /usr/sbin/grub-probe
If any of these is a symbolic link to /bin/true then something's wrong.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I have disabled the apport crash report service while remastering.Now it
is solves(no crash report seen)
--
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:
Hi Paul,
could you provide some more details?
I suppose you were using the 'uck-gui' command to remaster a Ubuntu
14.04.1 amd64 image?
How are you booting (DVD or USB)?
Did you boot right into the Live CD (by choosing Try Ubuntu)?
When and how exactly did you get this failure? (In fact while
@jox :
hi,
i was able to make the custom live cd with ur edited remaster-live-cd.sh
file, but while booting it from the live cd shows libpam-systemd
installation/upgradation failure.apport crash report pasted below :
ProblemType: Package
Architecture: amd64
Date: Thu Sep 11 11:06:58 2014
If you are remastering Linux Mint 17 XFCE then only editing /usr/sbin
/invoke-rc.d will do
--
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
I have investigated this some more. I will provide a solution for UCK
(Ubuntu Customization Kit) but it might apply to other contexts as well.
It is actually 3 distinct issues:
The main problem is the missing init scripts. This is a result from UCK
deactivating initctl (see also in the output of
Sorry, there is a typo (the .bak is wrong). Let me correct this:
--
You might also apply the attached patch as follows:
$ cd /usr/lib/uck
$ sudo patch -p2 remaster-live-cd.sh \
/path/to/fix-uck-missing-initd-scripts-1.patch
--
(Please note that I actually meant You might
I'm using UCK (Ubuntu Customization Kit) to create a custom 64-bit
Xubuntu 14.04 image.
same here.
For libpam-systemd and whoopsie I can workaround it by editing the following
files as described by hamish:
/var/lib/dpkg/info/whoopsie.prerm
/var/lib/dpkg/info/libpam-systemd\:amd64.prerm
I just ran into this a second time during a trusty update
--
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
I wonder if mounting /run in the chroot with --bind would help?
--
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
Steve C wrote:
I just ran into this a second time during a trusty update
yes, 14.04.1 was ok until there was again a new security update for the
package to upgrade to.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
I have this issue, not sure if it's related:
Setting up libpam-systemd:amd64 (204-5ubuntu20.4) ...
start: Job failed to start
invoke-rc.d: initscript systemd-logind, action start failed.
dpkg: error processing package libpam-systemd:amd64 (--configure):
subprocess installed post-installation
This is fixed in utopic, as the init script went away completely, in
favor of always using D-BUS activation.
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Utopic)
Importance: High
Status: Confirmed
** Changed in:
I get this issue with a chroot ubuntu 14.04 armhf build running with
android on a samsung galaxy tab 10.1.
--
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:
47 matches
Mail list logo
