'sudo' errors with beta 135 update

[DennisLfromGA]

With the the last beta 135 update (16209.17 / 135.0.7049.19) I'm having issues with 'sudo' and cannot remove rootfs verification among other things involving 'sudo'.

The current bootpair B (beta 135) shown below is exhibiting the 'sudo' error issues, the previous bootpair A (beta 134) does not.

>       CURRENT_BOOTPAIR=B                         ALTERNATE_BOOTPAIR=A
>       -------------------------------------                        ----------------------------------------
>       CURRENT_KERNEL=4                            ALTERNATE_KERNEL=2
>       CURRENT_ROOT=/dev/mmcblk0p5        ALTERNATE_ROOT=/dev/mmcblk0p3
>       CURRENT_MILESTONE=135                  ALTERNATE_MILESTONE=134
>       CURRENT_CHROME=135.0.7049.19      ALTERNATE_CHROME=134.0.6998.94
>       CURRENT_RELEASE=16209.17.0          ALTERNATE_RELEASE=16181.37.0
>       CURRENT_KERNVER=6.6.73-07388      ALTERNATE_KERNVER=6.6.69-06720
>       CURRENT_TRACK=beta-channel            ALTERNATE_TRACK=beta-channel

I can alternate bootpairs so I'm not quite out of options ATM but hopefully, this new behavior is a glitch and not something intended.

When I try to remove rootfs verification I get the following error about 'undefined symbol: sudo_strlcpy':

>       /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions 4
>       sudo: symbol lookup error: sudo: undefined symbol: sudo_strlcpy
>       make_dev_ssd.sh: ERROR: Failed to get partition 4 offset from /dev/mmcblk0

Even the --force option fails with the same 'undefined symbol: sudo_strlcpy' error:

>       Removal of rootfs verification failed, now we'll try using the '--force' option...
>       /usr/share/vboot/bin/make_dev_ssd.sh --force --remove_rootfs_verification --partitions 4
>
>             !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>             ! INFO: ALL VALIDITY CHECKS WERE BYPASSED. YOU ARE ON YOUR OWN. !
>             !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>            
>       sudo: symbol lookup error: sudo: undefined symbol: sudo_strlcpy
>       make_dev_ssd.sh: ERROR: Failed to get partition 4 offset from /dev/mmcblk0
>       Sorry but REMOVAL of rootfs verification failed on partition /dev/mmcblk0p5/4.
>       sudo: symbol lookup error: sudo: undefined symbol: sudo_strlcpy

Even trying to get the sudo version fails:

>       sudo -V
>       sudo: symbol lookup error: sudo: undefined symbol: sudo_strlcpy

So, for now, I'm having to use the previously installed beta 134 version (16181.37.0 / 134.0.6998.94) to do anything involving 'sudo'.
I am guessing that the sudo utility / sudo library version has changed or maybe the updated kernel version is the culprit but I cannot verify that.

Please let me know if anyone else is experiencing this glitch, hopefully, I'm not the only one and this issue can be reproduced & addressed soon.

BTW: This is happening on my Pixelbook / Eve, I haven't tested it on my other Chromebooks yet.

Thanx,
~DennyL

[Mike Frysinger]

assuming this is an official build ...

i assume you ran `dev_install` and have content in /usr/local.  this will include additional libraries.  they are not guaranteed to be stable across releases, and we don't really have a story for upgrading it cleanly.  you could try running `unset LD_LIBRARY_PATH` before running `sudo -V` and see if that helps.  then you could reinstall with `dev_install --force`.

otherwise, please file a bug for it.

https://issuetracker.google.com/issues/new?component=1037860

-mike

--
--
ChromiumOS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss

[DennisLfromGA]

Thanx Mike for the guidance.

I `unset LD_LIBRARY_PATH` before running `sudo -V` and it comes back empty, no version info.
After I unset it the command `/usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions 2` still comes back with the sudo_strlcpy error.

This issue has now propagated to my Framework Chromebook / Banshee on beta 135 so I have filed a feedback report and  an issuetracker bug.

Thanx again,
~DennyL