Stonking 26.10 sudo does not work while sudo.ws still works

Project Discussion Pre-Release Discussion
1

Installed stonking 26.10 from Dangerous ISO dated Aug 28 sudo refuses working with a message: sudo: sudo must be owned by uid 0 and have the setuid bit set

reported bug: Bug #2165419 “sudo: sudo must be owned by uid 0 and have the set...” : Bugs : sudo package : Ubuntu

2 Likes
2

Was already covered in this bug report. Yours was marked as a duplicate.

1 Like
3

I just received a fix and now sudo-rs works fine but this seems ignored in the launchpad bugs.

4

That is categorically false. Bug reports aren’t places to receive support, nor should you always expect a response directly. Just because someone isn’t talking to you in that bug report doesn’t mean they didn’t see you, just that nothing you said added anything meaningful to the conversation. If you actually read that bug report, you’ll notice that the people who are working on the issue, well in advance of you even knowing about the issue, already had fixes ready to go.

Once you report a bug, unless someone asks you for more information, it’s more or less hands-off while the people who work on it fix it, unless you’re one of the people willing to work on it.

2 Likes
5

I mean: i received a fix and now sudo works fine why the bug status is still ‘in progress’?

6

Because bugs aren’t about you personally; they’re about what the status is in the greater scheme of things. Bugs are only bugs when they’re reproducible and are only fixed when they hit the -release or -updates pockets. Just because you have a solution and a fix doesn’t mean others aren’t affected still.

7

Waiting for fix sudo.ws has no problem an can be used instead sudo and also to apply a workaround:

corrado@corrado-ns5-sd-0901:~$ cd /bin
corrado@corrado-ns5-sd-0901:/bin$ sudo.ws chmod u+s sudo-rs
[sudo] password for corrado: 
corrado@corrado-ns5-sd-0901:/bin$ sudo.ws chmod u+s sudo
corrado@corrado-ns5-sd-0901:/bin$

now sudo and sudo-rs are ok

corrado@corrado-ns5-sd-0901:~$ sudo apt update
[sudo: authenticate] Password: 
Hit:1 http://it.archive.ubuntu.com/ubuntu stonking InRelease
....

Can I add this note to the bug report? Might it be useful?

8

It will not be useful at all. The fix was was in the mechanism in which the .iso file was built in addition to rust-coreutils. If you look at the bug report, it says “fix released” in the upstream rust-coreutils and the package in Ubuntu says fix committed meaning it’s been uploaded and making its way through stonking-proposed which requires tests by autopkgtests to pass before it lets it migrate to stonking-release. All you can and should do is be patient and let the people working on it do their job.

9

The problem affects not only the LIVE sessions but also everyone who installed Stonking from recent ISOs and cannot update using `sudo apt`.

10

…which is unsupported anyhow. There’s enough info on that bug report for a workaround.

Besides that, bug reports aren’t about providing support or helping people around the problem, but are about fixing what is wrong to begin with.

1 Like