On a recent update, `sudo` got upgraded from sudo-1.9.6_p1-r2 to sudo-1.9.8_p2. Since then, any call to `sudo` other than `sudo
--help` resulted in a Segmentation Fault. I have tried remerging sudo
again or remerging the PAM-related dependencies, but it did not help. Switching back to 1.9.6, however, resulted in a working sudo.
Is it just me, or has anybody else seen a similar problem?
Is it just me, or has anybody else seen a similar problem?
On a recent update, `sudo` got upgraded from sudo-1.9.6_p1-r2 to sudo-1.9.8_p2. Since then, any call to `sudo` other than `sudo
--help` resulted in a Segmentation Fault. I have tried remerging sudo
again or remerging the PAM-related dependencies, but it did not help. Switching back to 1.9.6, however, resulted in a working sudo.
Is it just me, or has anybody else seen a similar problem?
Best,
Anton
Works fine for me. Can you try it with strace to see if you can tell
where it crashes? That or emerge with sufficient debug info that you
can run it under gdb and get a backtrace?
On Tue, 2021-11-09 at 22:36 +0200, Anton wrote:
Is it just me, or has anybody else seen a similar problem?
Working fine here, with the following USE set:
USE="-gcrypt -ldap nls offensive pam -sasl secure-path (-selinux)
sendmail -skey ssl -sssd" ABI_X86="(64)"
I wonder if your issue isn't related to updated PAM libraries. The
post emerge messages for PAM suggest either rebooting or restarting
certain services after upgrades.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 89:57:43 |
Calls: | 6,658 |
Files: | 12,203 |
Messages: | 5,334,088 |