From: Fredrik Salomonsson <plattfot@posteo.net>
To: help-guix <help-guix@gnu.org>
Subject: pam-u2f and glibc issues
Date: Wed, 11 Sep 2024 17:07:33 +0000 [thread overview]
Message-ID: <87a5geruei.fsf@posteo.net> (raw)
Hi,
Encountered a strange issue when I did a system update this weekend.
My u2f login stopped working for swaylock. I checked the
/var/log/secure and found:
```
Sep 9 20:17:38 localhost swaylock: PAM unable to dlopen(/gnu/store/hnih46irf9zjwn8fvqka2wryb2m4y71g-pam-u2f-1.0.8/lib/security/pam_u2f.so): /gnu/store/ln6hxqjvz6m9gdd9s97pivlqck7hzs99-glibc-2.35/lib/libc.so.6: version `GLIBC_2.38' not found (required by /gnu/store/hnih46irf9zjwn8fvqka2wryb2m4y71g-pam-u2f-1.0.8/lib/security/pam_u2f.so)
Sep 9 20:17:38 localhost swaylock: PAM adding faulty module: /gnu/store/hnih46irf9zjwn8fvqka2wryb2m4y71g-pam-u2f-1.0.8/lib/security/pam_u2f.so
Sep 9 20:17:38 localhost swaylock: PAM unable to dlopen(/gnu/store/xcmvyjzf69xfpbpahncskblyybg5b5cp-elogind-252.9/lib/security/pam_elogind.so): /gnu/store/ln6hxqjvz6m9gdd9s97pivlqck7hzs99-glibc-2.35/lib/libm.so.6: version `GLIBC_2.39' not found (required by /gnu/store/xcmvyjzf69xfpbpahncskblyybg5b5cp-elogind-252.9/lib/security/pam_elogind.so)
Sep 9 20:17:38 localhost swaylock: PAM adding faulty module: /gnu/store/xcmvyjzf69xfpbpahncskblyybg5b5cp-elogind-252.9/lib/security/pam_elogind.so
```
Looks like something is still running glibc@2.35 (linux-pam?) and trying
to load pam_u2f which is built with glibc@2.39 (and also pam_elogind
with the same result). I'm not sure how to track down what is still
using glibc@2.35. I checked with `guix refresh -T` for both pam-u2f and
linux-pam and both report depending on 2.39.
Here is what `guix describe` reports:
```
Generation 114 sep 08 2024 20:17:45 (current)
plt 69ca530
repository URL: https://git.sr.ht/~plattfot/plt
branch: master
commit: 69ca530fc3f00077898b6d55ecd623d5c2adc590
guix 056910e
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 056910ec864cb7cf3225a0c27679d94405db7dcd
nonguix e6b3bb8
repository URL: https://gitlab.com/nonguix/nonguix
branch: master
commit: e6b3bb87a46024cd6b2fb1a1cad1387de0053f44
```
And I reconfigured my system using:
```
sudo guix system reconfigure -e '(@ (plt system machines heimdal) plt-heimdal-os)'
```
I.e. using this config[0].
I tested using the linux-libre kernel, the defaults for the firmware etc
and encountered the same issue. So I don't think it's coming from any
of the other channels. Anyone have any idea how I can track this down?
Thanks
[0] https://git.sr.ht/~plattfot/plt/tree/69ca530fc3f00077898b6d55ecd623d5c2adc590/item/plt/system/machines/heimdal.scm
--
s/Fred[re]+i[ck]+/Fredrik/g
reply other threads:[~2024-09-11 17:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5geruei.fsf@posteo.net \
--to=plattfot@posteo.net \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).