yabai-v7.1.16
ProductName: macOS
ProductVersion: 26.1
BuildVersion: 25B78
Description
I am unable to destroy spaces using yabai -m space --destroy. The command fails silently with no output and no error in the log, even though the space is empty and not focused.
Conversely, yabai -m space --create works perfectly, which suggests the Scripting Addition is loaded and SIP is configured correctly.
Environment
- **Yabai version: yabai-v7.1.16
- **macOS version: macOS
- SIP: Disabled (fs, debug, nvram)
- Scripting Addition: Loaded but i get the following:
sudo: sorry, you are not allowed to set the following environment variables: TERMINFO
Steps to reproduce
- Create a new space:
yabai -m space --create (Success: Space created)
- Focus the new space.
- Attempt to destroy it:
yabai -m space --destroy (Fail: Nothing happens)
- Focus a different space and attempt to destroy the target space:
yabai -m space N --destroy (Fail: Nothing happens)
Logs
tail -f /tmp/yabai_$USER.err.log returns no the following output, which i do not understand:
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
- No errors appear in stderr when running the destroy command.
- Previous
TERMINFO sudo errors were resolved via sudoers config; the silent failure persists.
Notes
It seems like the private API hook for destroying spaces might have changed in macOS Tahoe, while the creation hook remains valid.
yabai-v7.1.16
ProductName: macOS
ProductVersion: 26.1
BuildVersion: 25B78
Description
I am unable to destroy spaces using
yabai -m space --destroy. The command fails silently with no output and no error in the log, even though the space is empty and not focused.Conversely,
yabai -m space --createworks perfectly, which suggests the Scripting Addition is loaded and SIP is configured correctly.Environment
sudo: sorry, you are not allowed to set the following environment variables: TERMINFOSteps to reproduce
yabai -m space --create(Success: Space created)yabai -m space --destroy(Fail: Nothing happens)yabai -m space N --destroy(Fail: Nothing happens)Logs
tail -f /tmp/yabai_$USER.err.logreturns no the following output, which i do not understand:TERMINFOsudo errors were resolved via sudoers config; the silent failure persists.Notes
It seems like the private API hook for destroying spaces might have changed in macOS Tahoe, while the creation hook remains valid.