Thanks for the greatly detailed bug report Fabian! Losing sudo access is a considerable issue. I attempted to reproduce this upgrade on a fresh Noble image, however that had the correct permissions (4755) after the upgrade, including the setuid bit. In this case it seems that there must be some other reproduction step that is missing for the bug.
There was a recent issue on Stonking related to the rust-coreutils which caused this problem, however that should not affect upgrades from Noble to Resolute. There is also a similar bug that got fixed for sudo-rs related to the setuid bit: https://bugs.launchpad.net/ubuntu/+source/rust-sudo-rs/+bug/2125731 Would you mind making a .tar.gz file of your /var/log/dist-upgrade/ directory so that we can investigate whether something else interfered? Please make sure to leave out any potentially sensitive information in that case. All the best, Simon ** Changed in: rust-sudo-rs (Ubuntu) Status: New => Incomplete ** Changed in: rust-sudo-rs (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2166958 Title: sudo-rs and su-rs alternatives activated without setuid bit set after 24.04 -> 26.04 LTS do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-sudo-rs/+bug/2166958/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
