Incomplete linking with boost_regex
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gce-compute-image-packages (Ubuntu) |
Fix Released
|
Critical
|
Daniel Axtens | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
SRU Justification
=================
[Impact]
oslogin fails on Xenial and Trusty.
In auth.log we see:
Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(
Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_
Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(
Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_
The error message is a bit deceptive - PAM tries to load the module from the correct location, fails, and then tries the other location where it is missing. It then reports the missing error rather than the real error.
symlink the module into both paths leads to a much more useful error message:
Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(
Oct 18 06:45:12 dja-202158 sshd[16554]: PAM adding faulty module: pam_oslogin_
Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(
[Test case]
- set up GCE VM
- turn on oslogin
- attempt to log in
[Fix]
debian/
[Regression Potential]
- fixes a regression
- limited to oslogin, and how it is linked.
[Other Notes]
We still see a scary list of warnings when building, but they don't seem to have an impact on the common path:
dpkg-shlibdeps: warning: symbol _ZN5boost9re_
dpkg-shlibdeps: warning: symbol _ZN5boost9re_
dpkg-shlibdeps: warning: symbol _ZNK5boost9re_
dpkg-shlibdeps: warning: symbol _ZN5boost13matc
dpkg-shlibdeps: warning: symbol _ZN5boost9re_
dpkg-shlibdeps: warning: symbol _ZN5boost11basi
dpkg-shlibdeps: warning: symbol _ZN5boost9re_
dpkg-shlibdeps: warning: symbol _ZNK5boost9re_
dpkg-shlibdeps: warning: symbol _ZN5boost9re_
dpkg-shlibdeps: warning: symbol _ZN5boost9re_
Related branches
- Thomas Ward (community): Approve
- Balint Reczey (community): Approve
- Andreas Hasenack: Abstain
-
Diff: 51 lines (+29/-0)3 files modifieddebian/changelog (+8/-0)
debian/patches/series (+1/-0)
debian/patches/set-LDFLAGS-for-PAM.patch (+20/-0)
- Thomas Ward (community): Approve
- Andreas Hasenack: Abstain
- Balint Reczey (community): Approve
-
Diff: 51 lines (+29/-0)3 files modifieddebian/changelog (+8/-0)
debian/patches/series (+1/-0)
debian/patches/set-LDFLAGS-for-PAM.patch (+20/-0)
tags: | added: sts |
tags: | added: patch |
affects: | linux (Ubuntu) → gce-compute-image-packages (Ubuntu) |
tags: | added: id-5bc9b862a6ff8a053b9d2fce |
tags: |
added: verification-done removed: verification-needed |
tags: | added: id-5bce0e6bdfc4204c892f4324 |
Hello Daniel, or anyone else affected,
Accepted gce-compute- image-packages into trusty-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ gce-compute- image-packages/ 20180905+ dfsg1-0ubuntu1~ 14.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- trusty to verification- done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- trusty. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.