I could reproduce locally and find the issue.
This is a really major break in the `env` program: it doesn't re-execute
with the subcommand, instead it forks! So then terminating the env
process keeps the subcommand running. This affects all scripts whose
shebang uses /usr/bin/env.
Think of any systemd-managed python daemon; now stopping the service
doesn't terminate the daemon if its shebang looks like `#!/usr/bin/env
python3`.
** Changed in: coreutils-from (Ubuntu)
Status: New => Triaged
** Changed in: pipewire (Ubuntu)
Status: New => Invalid
** Changed in: mutter (Ubuntu)
Status: In Progress => Invalid
** Changed in: rust-coreutils (Ubuntu)
Status: New => Triaged
** Changed in: rust-coreutils (Ubuntu)
Importance: Undecided => Critical
** Changed in: rust-coreutils (Ubuntu)
Milestone: None => ubuntu-25.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112491
Title:
mutter & gnome-shell: FTBFS with coreutils-from: pipewire stuck in an
accept4 loop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils-from/+bug/2112491/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
