Same root cause as https://bugs.launchpad.net/ubuntu/+source/rust-sudo- rs/+bug/2150073 . With use_pty, the monitor resumes only the command pid with kill(), so the editor that visudo or the inner sudo -e starts stays in T+ after fg. Upstream PR 1530 (commit 1c9a1eb2) fixes it with killpg(), and closed upstream issue 1527.
Tested in fresh ubuntu:26.04 containers on a pty, as root and as a NOPASSWD user, nano as the editor, Ctrl-T Ctrl-Z, then fg, then Ctrl-X: * "sudo sudo -e /etc/FILE": on 0.2.13-0ubuntu1.2 the inner "sudo -e" child and the editor stay in T+. With PR 1530 both resume and Ctrl-X ends with "sudo: /etc/FILE unchanged". * "sudo visudo": on 0.2.13-0ubuntu1.2 /usr/bin/editor stays in T+. With PR 1530 nano comes back and Ctrl-X ends with "visudo: /tmp/sudoers-XXXXXX/sudoers unchanged". The debdiff for resolute (0.2.13-0ubuntu1.3, closes this bug, 2150073 and 2146860) and the full test record are on https://bugs.launchpad.net/ubuntu/+source/rust-sudo-rs/+bug/2150073 . The SRU template is in this bug's description. The development task can be set to Fix Released (fixed in 0.2.14, first released as 0.2.14-1ubuntu2 in stonking, tenacious has 0.2.14-1ubuntu4.1), and it needs a Resolute task. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2160212 Title: SIGCONT doesn't seem to propagate all the way through in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-sudo-rs/+bug/2160212/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
