[Touch-packages] [Bug 1382510] Re: systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch
I've installed packages:
http://launchpadlibrarian.net/188726673/libsystemd-daemon0_204-5ubuntu20.8_amd64.deb
http://launchpadlibrarian.net/188726662/systemd-services_204-5ubuntu20.8_amd64.deb
http://launchpadlibrarian.net/188727128/libpam-systemd_204-5ubuntu20.8_i386.deb
http://launchpadlibrarian.net/18872/libpam-systemd_204-5ubuntu20.8_amd64.deb
and the issue is resolved for me.
Thanks.
--
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/1382510
Title:
systemd-logind upstart script breaks if libpam-systemd is installed
for more than one arch
Status in “systemd” package in Ubuntu:
Fix Released
Status in “systemd” source package in Trusty:
Fix Committed
Bug description:
/etc/init/systemd-logind.conf contains the following:
# only start if PAM module is actually available, not if libpam-systemd is
# removed but not purged
[ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; }
Which is a wrongly written script. It assumes that there is at most one file
matching the wildcard. It is not true in my system.
If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then:
# ls /lib/*/security/pam_systemd.so
/lib/i386-linux-gnu/security/pam_systemd.so
/lib/x86_64-linux-gnu/security/pam_systemd.so
and you get the following:
# cat /var/log/upstart/systemd-logind.log
/proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so:
unexpected operator
systemd-logind stop/pre-start, process 2462
systemd-logind does not start at all. This causes many bad things to
happen later.
There are many ways to fix this. For my purposes I removed the faulty
line from the file. I don't know what is the expected behaviour. Maybe
this one:
ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; }
This bug might be the root cause of other bugs. Like this one:
#1372187 (and #1377727)
SRU TEST CASE
=
- On an amd64 system, run sudo apt-get install libpam-systemd:i386
- Then run sudo restart systemd-logind
- On current trusty this will result in stop/waiting, with the error in
/var/log/upstart/systemd-logind.log as above.
- With this fix this will result in start/running and no error.
My system info:
# lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
# apt-cache policy libpam-systemd
libpam-systemd:
Installed: 204-5ubuntu20.7
Candidate: 204-5ubuntu20.7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1382510/+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
[Touch-packages] [Bug 1382510] [NEW] systemd-logind upstart script is flawed
Public bug reported:
/etc/init/systemd-logind.conf contains the following:
# only start if PAM module is actually available, not if libpam-systemd is
# removed but not purged
[ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; }
Which is a wrongly written script. It assumes that there is at most one file
matching the wildcard. It is not true in my system.
If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then:
# ls /lib/*/security/pam_systemd.so
/lib/i386-linux-gnu/security/pam_systemd.so
/lib/x86_64-linux-gnu/security/pam_systemd.so
and you get the following:
# cat /var/log/upstart/systemd-logind.log
/proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected
operator
systemd-logind stop/pre-start, process 2462
systemd-logind does not start at all. This causes many bad things to
happen later.
There are many ways to fix this. For my purposes I removed the faulty
line from the file. I don't know what is the expected behaviour. Maybe
this one:
ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; }
This bug might be the root cause of other bugs. Like this one: #1372187 (and
#1377727)
My system info:
# lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04
# apt-cache policy libpam-systemd
libpam-systemd:
Installed: 204-5ubuntu20.7
Candidate: 204-5ubuntu20.7
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1382510
Title:
systemd-logind upstart script is flawed
Status in “systemd” package in Ubuntu:
New
Bug description:
/etc/init/systemd-logind.conf contains the following:
# only start if PAM module is actually available, not if libpam-systemd is
# removed but not purged
[ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; }
Which is a wrongly written script. It assumes that there is at most one file
matching the wildcard. It is not true in my system.
If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then:
# ls /lib/*/security/pam_systemd.so
/lib/i386-linux-gnu/security/pam_systemd.so
/lib/x86_64-linux-gnu/security/pam_systemd.so
and you get the following:
# cat /var/log/upstart/systemd-logind.log
/proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so:
unexpected operator
systemd-logind stop/pre-start, process 2462
systemd-logind does not start at all. This causes many bad things to
happen later.
There are many ways to fix this. For my purposes I removed the faulty
line from the file. I don't know what is the expected behaviour. Maybe
this one:
ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; }
This bug might be the root cause of other bugs. Like this one: #1372187 (and
#1377727)
My system info:
# lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
# apt-cache policy libpam-systemd
libpam-systemd:
Installed: 204-5ubuntu20.7
Candidate: 204-5ubuntu20.7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1382510/+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
[Touch-packages] [Bug 1375663] [NEW] curl handles EINTR wrong
Public bug reported: Our application using libcurl for http communication was behaving awkward and after thorough investigation we found that in some cases it doesn't retry a poll after EINTR. Later we found, that this is a bug in libcurl and that it was repaired in this upstream patch: https://github.com/bagder/curl/commit/97d2e4bd75d1be26b48f37900b7b719c418e0ac6 # lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 # apt-cache policy curl curl: Installed: 7.35.0-1ubuntu2.1 Candidate: 7.35.0-1ubuntu2.1 ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Patch added: fix_timeout_return_value.patch https://bugs.launchpad.net/bugs/1375663/+attachment/4220043/+files/fix_timeout_return_value.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1375663 Title: curl handles EINTR wrong Status in “curl” package in Ubuntu: New Bug description: Our application using libcurl for http communication was behaving awkward and after thorough investigation we found that in some cases it doesn't retry a poll after EINTR. Later we found, that this is a bug in libcurl and that it was repaired in this upstream patch: https://github.com/bagder/curl/commit/97d2e4bd75d1be26b48f37900b7b719c418e0ac6 # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy curl curl: Installed: 7.35.0-1ubuntu2.1 Candidate: 7.35.0-1ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1375663/+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
