[Bug 2127766] Re: snap run --strace doesn't work with sudo-rs [sudo -E not supported]

Maciej Borzecki 2127766 at bugs.launchpad.net
Thu Oct 30 09:05:20 UTC 2025


I'm adding a workaround in snapd which should make this problem, and a
couple of others like running sudo in a new session,  go away and make
snap run --strace work again.

** Changed in: snapd
     Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)

** Changed in: snapd
    Milestone: None => 2.73

** Changed in: snapd
       Status: New => In Progress

-- 
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/2127766

Title:
  snap run --strace doesn't work with sudo-rs [sudo -E not supported]

Status in snapd:
  In Progress
Status in rust-sudo-rs package in Ubuntu:
  Won't Fix
Status in snapd package in Ubuntu:
  New

Bug description:
  sudo-rs became the default sudo in 25.10, which broke this snap run
  --strace,

  $ snap run --strace <snap>.<app>
  warning: preserving the entire environment is not supported, `-E` is ignored
  [sudo: authenticate] Password: 
  error: exit status 1

  It does work if I switch back to GNU Coreutils' sudo. The reason being
  many required environment variables are no longer passed through, and
  the strace fails due to SNAP_INSTANCE_NAME not being set, before we
  get to execve'ing the snap application itself.

  I commented on this use case in the sudo-rs issue tracker:
  https://github.com/trifectatechfoundation/sudo-rs/issues/1299

  Maybe snapd needs to have a whitelist of environment variables?

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2127766/+subscriptions




More information about the foundations-bugs mailing list