| 1 |
On 11/9/2021 11:59 PM, Matt Connell (Gmail) wrote: |
| 2 |
> On Tue, 2021-11-09 at 22:36 +0200, Anton wrote: |
| 3 |
>> Is it just me, or has anybody else seen a similar problem? |
| 4 |
> |
| 5 |
> Working fine here, with the following USE set: |
| 6 |
> |
| 7 |
> USE="-gcrypt -ldap nls offensive pam -sasl secure-path (-selinux) |
| 8 |
> sendmail -skey ssl -sssd" ABI_X86="(64)" |
| 9 |
> |
| 10 |
> I wonder if your issue isn't related to updated PAM libraries. The |
| 11 |
> post emerge messages for PAM suggest either rebooting or restarting |
| 12 |
> certain services after upgrades. |
| 13 |
> |
| 14 |
> |
| 15 |
I thought so too, but neither reboot, nor re-merging the PAM libraries |
| 16 |
made a difference. To be fully honest, for "re-merging the PAM |
| 17 |
libraries" I only looked at the immediate dependencies, so there's some |
| 18 |
room for error there. Still, I think the best next step is to try what |
| 19 |
others suggested: study the strace or the core file to try to understand |
| 20 |
in which library the problem occurres. |
Archives