• [gentoo-user] sudo-1.9.8_p2 produces Segmentation Fault on any use

    From Anton@21:1/5 to All on Tue Nov 9 21:40:03 2021
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tastytea@21:1/5 to anton.stay.connected@gmail.com on Tue Nov 9 22:30:02 2021
    On 2021-11-09 22:36+0200 Anton <anton.stay.connected@gmail.com> wrote:

    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?

    I'm using it for about a week without problems. Compiled with
    USE="nls pam secure-path sendmail ssl -gcrypt -ldap -offensive -sasl
    (-selinux) -skey -sssd"

    Kind regards, tastytea

    --
    Get my PGP key with `gpg --locate-keys tastytea@tastytea.de` or at <https://tastytea.de/tastytea.asc>.

    -----BEGIN PGP SIGNATURE-----

    iHUEAREKAB0WIQQ1VSZoZMptf/RapufPw5SX8bJuBwUCYYrm1gAKCRDPw5SX8bJu B74iAQCCsWRCTeQlhvkxlH+2qifTvXYnDSCwklFhq8e0TqCSOQD+LzyqXOD/TmQB HQUIAgUs+Ut30o9/P0RiTAH2YcKFyUQ=
    =VAGN
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Matt Connell (Gmail)@21:1/5 to Anton on Tue Nov 9 23:00:04 2021
    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jack@21:1/5 to Anton on Tue Nov 9 22:30:01 2021
    On 2021.11.09 15:36, Anton wrote:
    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?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anton@21:1/5 to Jack on Wed Nov 10 18:10:01 2021
    On 11/9/2021 11:27 PM, Jack wrote:
    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?

    Thanks, I'll try that when I have a suitably large chunk of free time.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anton@21:1/5 to All on Wed Nov 10 18:10:02 2021
    On 11/9/2021 11:59 PM, Matt Connell (Gmail) wrote:
    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.


    I thought so too, but neither reboot, nor re-merging the PAM libraries
    made a difference. To be fully honest, for "re-merging the PAM
    libraries" I only looked at the immediate dependencies, so there's some
    room for error there. Still, I think the best next step is to try what
    others suggested: study the strace or the core file to try to understand
    in which library the problem occurres.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)