[Bug 2150073] Re: sudo‑rs causes apt-get (install or upgrade)to be stopped (T+) in a non‑interactive SSH session

[KJ LAU]

hi Johnsson, thx for looking into this issue, below is my elaboration
and flow to reproduce the issue.

Flow to reproduce the issue:

download u26.04 image script 
  -> called boot_image_via_qemu script
       -> called expect script to launch installer script in guest with sudo priveledge
            -> installer script running in guest (do_signal_stop)

Script elaboration:

boot_image_via_qemu script:
this script will boot the downloaded image in qemu and pass the installer.sh into u26.04 Guest   

expect script:
this script will interface and pass in the credential and login into ubuntu image  in and  launch installer in Guest with sudo privilege

installer script: 
This script will run apt-get up && upgrade-y  and install some packages 

function performUpdateNUpgrade()
{
        apt-get update && apt-get upgrade -y
        apt-get install ethtool libbpf1 lm-sensors -y
}

performUpdateNUpgrade

observation in Guest:
Stucked Processing triggers for man-db (2.13.1-1build1)…

Unpacking lm-sensors (1:3.6.2-2build1)…
Setting up lm-sensors (1:3.6.2-2build1)…
Created symlink '/etc/systemd/system/multi-user.target.wants/lm-sensors.service' → '/usr/lib/systemd/system/lm-sensors.service'.
Processing triggers for man-db (2.13.1-1build1)…


user at localhost:~$ sudo ps -eo pid,ppid,stat,wchan:32,cmd | egrep 'apt|dpkg|ldconfig'
   8368    8275 T+   do_signal_stop                   apt-get install ethtool libbpf1 lm-sensors -y



no, i don't change anything in /etc/sudoers

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rust-sudo-rs in Ubuntu.
https://bugs.launchpad.net/bugs/2150073

Title:
  sudo‑rs causes apt-get (install or upgrade)to be stopped (T+) in a
  non‑interactive SSH session

Status in rust-sudo-rs package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 26.04 (where /usr/bin/sudo is implemented via sudo-rs), running apt-get upgrade or install under sudo from a non‑interactive SSH + Expect‑driven environment causes the apt-get process to enter a T+ (stopped) state due to do_signal_stop(), causing the installation to hang indefinitely.
  This problem does not reproduce when replacing sudo-rs with classic sudo (sudo.ws) under identical conditions.

  High level flow:

  Host OS (launcher):
    Ubuntu 22.04 LTS

  Guest OS (QEMU VM):
    Ubuntu 26.04 (daily / pre‑release)

  user at localhost:~$ sudo --version
  sudo-rs 0.2.13-0ubuntu1

  sudo implementation:
    - Failing: sudo-rs (default sudo in Ubuntu 26.04)
    - Working: classic sudo (sudo.ws)

  Invocation context:
    SSH non‑interactive session
    Command chain driven via shell script + Expect
    No human‑attached TTY inside the guest

  Guest OS debug information:

  sudo ps -eo pid,ppid,stat,wchan:32,cmd | egrep 'apt|dpkg|ldconfig' | grep -v grep
     8809    7947 T+   do_signal_stop                   apt-get upgrade -y

  pstree -ap output:

    ├─sshd,3270
    │   ├─sshd-session,3757
    │   │   └─sshd-session,3793
    │   │       └─bash,3799
    │   │           ├─sudo,3960 ./installer.sh ASL default
    │   │           │   └─sudo,3964 ./installer.sh ASL default
    │   │           │       └─installer.sh,3966 /home/user/installer.sh ASL default
    │   │           │           ├─installer.sh,7947 /home/user/installer.sh ASL default
    │   │           │           │   └─apt-get,8809 upgrade -y
    │   │           │           └─tee,7948 -a /home/user/cbkc_output.log
    │   │           └─tee,3961 installer_logs.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-sudo-rs/+bug/2150073/+subscriptions