Space focusing issues with Sonoma 14.1 (23B74) #1937

doadam · 2023-10-26T11:56:40Z

Since upgrading to Sonoma 14.1 (build 23B74), there are 2 new issues which I didn't have before (I was on Sonoma 14.0 previously):

Space focus doesn't work unless the source display and destination display are different
Space focusing is animated, where it used to just be instant. This is also the case with yabai -m config window_animation_duration 0.0. It used to be instant without this as well.

Here's my config file:

#!/usr/bin/env bash

# Disable Apple's shitty window manager
launchctl unload -F /System/Library/LaunchAgents/com.apple.WindowManager.plist > /dev/null 2>&1 &

sudo yabai --load-sa
yabai -m signal --add event=dock_did_restart action="sudo yabai --load-sa"

# global settings
yabai -m config debug_output on

yabai -m config mouse_follows_focus          on
yabai -m config focus_follows_mouse          autoraise

yabai -m config window_placement             second_child
yabai -m config window_topmost               off

yabai -m config window_opacity               off
yabai -m config window_opacity_duration      0.0
yabai -m config window_shadow                on

yabai -m config active_window_opacity        1.0
yabai -m config normal_window_opacity        0.90
yabai -m config split_ratio                  0.50
yabai -m config auto_balance                 off

# Mouse support
yabai -m config mouse_modifier               alt
yabai -m config mouse_action1                move
yabai -m config mouse_action2                resize

# general space settings
yabai -m config layout                       stack
yabai -m config top_padding                  0
yabai -m config bottom_padding               0
yabai -m config left_padding                 0
yabai -m config right_padding                0
yabai -m config window_gap                   0

I also tried installing from HEAD (#40d1075) but this had no effect.

Needless to say, SIP is disabled (everything worked fine on 14.0 for me). Here's the output from csrutil:

csrutil status                                                                                                                                                                                                                         
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: enabled
	Filesystem Protections: disabled
	Debugging Restrictions: disabled
	DTrace Restrictions: enabled
	NVRAM Protections: disabled
	BaseSystem Verification: enabled
	Boot-arg Restrictions: disabled
	Kernel Integrity Protections: enabled
	Authenticated Root Requirement: enabled

I also enabled debug prints, but nothing was printed when I tried switching spaces.

Let me know if any more information is needed.

The text was updated successfully, but these errors were encountered:

rwijtvliet · 2023-10-26T23:00:57Z

Suspected duplicate of #1936

doadam · 2023-10-27T10:49:29Z

Suspected duplicate of #1936

I also thought so, but I don't get this pop-up. Also the payload (which is the code that runs inside the Docker to my understanding) does work for other things like moving a window or changing stacked windows. This is why I believe it is not a duplicate, but we shall see.

liuduwei · 2023-10-27T11:06:11Z

Suspected duplicate of #1936

I also thought so, but I don't get this pop-up. Also the payload (which is the code that runs inside the Docker to my understanding) does work for other things like moving a window or changing stacked windows. This is why I believe it is not a duplicate, but we shall see.

i didn't get that pop-up too. i also thought that it's not a duplicate, because i run yabai -m space --focus prev in the console, there is no error or warning message output. if that pop-up show means scripting-addtion execute failed, the console will output corresponding messages when i run yabai -m space --focus prev.

kabaliwths · 2023-10-27T11:46:38Z

By the way, if you attempt to switch the focus to the same space you are currently on, you will receive the message 'Cannot focus an already focused space.' However, for any other action, whether it's by label or using the previous/next function, it doesn't work.

davidandradeduarte · 2023-10-29T00:06:18Z

I'm also having the exact same issue.

jakehamilton · 2023-10-29T11:35:25Z

I have just upgraded to Sonoma 14.1 and Yabai v6.0.0. I'm having the same issue with yabai -m space --focus next (or numbered workspace) not having any effect. I did not get a popup as #1936 mentions.

mescalas · 2023-10-29T21:25:50Z

Same issue here

dvrkoo · 2023-10-30T08:29:16Z

same issue here

TuralAsgar · 2023-10-30T08:55:27Z

@koekeishiya, I appreciate your all efforts on this open source.
How can we solve this problem?

denis-anashkin · 2023-10-30T10:02:31Z

same here. no popup with error also

ccimponeriu1996 · 2023-10-30T20:25:38Z

same here

philipphoertnagl · 2023-10-30T21:37:56Z

I posted a week ago, when I upgraded MacOS to Sonoma 14.0 that I had problems with yabai -m config focus_follows_mouse autofocus but then with upgrading yabai to 6.0 it seemed to be fixed, but now again, my focus does not switch when I hover with my mouse, although I did NOT upgrade MacOS to Sonoma 14.1. But when I restart my MacBook all seems to work again normally. So there might be still the issue, that some things over time get weird with Sonoma and yabai ....

simonemargio · 2023-10-31T07:29:10Z

I posted a week ago, when I upgraded MacOS to Sonoma 14.0 that I had problems with yabai -m config focus_follows_mouse but then with upgrading yabai to 6.0 it seemed to be fixed, but now again, my focus does not switch when I hover with my mouse, although I did NOT upgrade MacOS to Sonoma 14.1. But when I restart my MacBook all seems to work again normally. So there might be still the issue, that some things over time get weird with Sonoma and yabai ....

Same problem, Sonoma 14.0 + yabai 6.0.0, and autofocus with the mouse sometimes doesn't work and then strangely it starts working again. The only thing I've noticed is that this problem occurs when the Mac turns on from a Sleep state or similar.

hb0nes · 2023-10-31T09:38:26Z

+1, space switching doesn't work on Sonoma 14.1.

When I run yabai --verbose, this is the only thing that I see:

EVENT_HANDLER_DAEMON_MESSAGE: space --focus 1

When I use Mac's built in space-switching, that works and Yabai also broadcasts that event:

event_signal_flush: transmitting space_changed to 1 subscriber(s)

Rodion-Bozhenko · 2023-11-01T10:21:52Z

Same issue here

kalamov · 2023-11-01T11:08:37Z

Same issue here

rayjanoka · 2023-11-01T19:07:44Z

while we wait for a fix I was able to map my space switch keys here. I just had to disable the shortcuts in my .skhdrc first.

konstruktor227 · 2023-11-02T08:19:11Z

Same issue here on Sonoma 14.1 and yabai 6.0.0. Both space --create and space --focus commands seem to do nothing. Moving windows to spaces once they have been created via mission control is working fine though.

suinly · 2023-11-02T09:38:19Z

Same problem (Sonoma 14.1, yabai 6.0.0). But if you're in the space of a second display, switching to the first display works fine (with a space changing animation).

henrythor · 2023-11-02T11:13:08Z

You can also just remap your skhd to emit another keystroke, I for instance have space switching in MacOS linked to ctrl-left so I can do this:

alt - p : yabai -m space --focus prev || skhd -k "ctrl - left"
alt - n : yabai -m space --focus next || skhd -k "ctrl - right"

doadam · 2023-11-02T12:19:44Z

I'm using hammerspoon for key binding, and had Opt+number to switch to a specific space.
I have 2 displays and found a hacky workaround.
The animation is still there and there are some sleeps, but at least I can navigate spaces now:

-- Function to get the active space ID and a table of visible spaces
function getSpaceInfo()
    -- Execute the yabai command to fetch the JSON output
    local yabaiOutput = hs.execute(yabai_path .. " -m query --spaces")

    -- Decode the JSON output to a Lua table
    local spaces, decodeError = hs.json.decode(yabaiOutput)

    if not spaces then
        hs.printf("JSON decode err: %s", decodeError)
        return nil, nil
    end
    
    local focusedSpace = nil
    local visibleSpaces = {}
    
    -- Iterate through the spaces
    for _, space in ipairs(spaces) do
        if space["has-focus"] == true then
            focusedSpace = space
        end
        if space["is-visible"] == true then
            table.insert(visibleSpaces, space)
        end
    end

    return focusedSpace, visibleSpaces
end

function focus_space_id(space_id)
    yabai({"-m", "space", "--focus", '' .. space_id})
end

for k,v in pairs({'1', '2', '3', '4', '5', '6', '7', '8', '9', '10'}) do
    hs.hotkey.bind({"alt"}, '' .. k % 10, function()
        local focusedSpace, visibleSpaces = getSpaceInfo()

        if focusedSpace then
            local targetDisplay = math.ceil(tonumber(k) / 5)
            local currentDisplay = focusedSpace.display
            --print("targetDisplay: ", targetDisplay)
            --print("currentDisplay: ", currentDisplay)

            if targetDisplay == currentDisplay then
                -- If the target and current display are the same, focus another space first
                for _, space in ipairs(visibleSpaces) do
                    if space.display ~= currentDisplay then
                        --print("Focusing space ", space.index, " first")
                        focus_space_id(space.index)

                        hs.timer.doAfter(0.05, function()
                            focus_space_id(k)
                        end)

                        return
                    end
                end
            end

            -- Focus the requested space
            focus_space_id(k)
        end
    end)
end

henrythor · 2023-11-03T08:47:34Z

I'm using hammerspoon for key binding, and had Opt+number to switch to a specific space. I have 2 displays and found a hacky workaround. The animation is still there and there are some sleeps, but at least I can navigate spaces now:

-- Function to get the active space ID and a table of visible spaces
function getSpaceInfo()
    -- Execute the yabai command to fetch the JSON output
    local yabaiOutput = hs.execute(yabai_path .. " -m query --spaces")

    -- Decode the JSON output to a Lua table
    local spaces, decodeError = hs.json.decode(yabaiOutput)

    if not spaces then
        hs.printf("JSON decode err: %s", decodeError)
        return nil, nil
    end
    
    local focusedSpace = nil
    local visibleSpaces = {}
    
    -- Iterate through the spaces
    for _, space in ipairs(spaces) do
        if space["has-focus"] == true then
            focusedSpace = space
        end
        if space["is-visible"] == true then
            table.insert(visibleSpaces, space)
        end
    end

    return focusedSpace, visibleSpaces
end

function focus_space_id(space_id)
    yabai({"-m", "space", "--focus", '' .. space_id})
end

for k,v in pairs({'1', '2', '3', '4', '5', '6', '7', '8', '9', '10'}) do
    hs.hotkey.bind({"alt"}, '' .. k % 10, function()
        local focusedSpace, visibleSpaces = getSpaceInfo()

        if focusedSpace then
            local targetDisplay = math.ceil(tonumber(k) / 5)
            local currentDisplay = focusedSpace.display
            --print("targetDisplay: ", targetDisplay)
            --print("currentDisplay: ", currentDisplay)

            if targetDisplay == currentDisplay then
                -- If the target and current display are the same, focus another space first
                for _, space in ipairs(visibleSpaces) do
                    if space.display ~= currentDisplay then
                        --print("Focusing space ", space.index, " first")
                        focus_space_id(space.index)

                        hs.timer.doAfter(0.05, function()
                            focus_space_id(k)
                        end)

                        return
                    end
                end
            end

            -- Focus the requested space
            focus_space_id(k)
        end
    end)
end

FYI to get the current space you can use yabai -m query --spaces --space and to get the spaces on the current display you can do yabai -m query --displays --display | jq -c '.spaces'

You could get the next space up or down by doing yabai -m query --spaces --space | jq -c '.index + 1' / yabai -m query --spaces --space | jq -c '.index - 1' and you could check if that space is within your current display's list of spaces using something like if [ $(jq --null-input --argjson spaces "$SPACES" -c --argjson next_space "$NEXT_SPACE" '$next_space|IN($spaces[])') = "true" ]; then ... fi

All things I used to do when yabai was working for me :P

suinly · 2023-11-03T11:00:32Z

The animation is still there

@henrythor I hope this is helpful. I changed the animation in System Preferences - Accessibility - Display - Reduce Motion. This is not a complete disabling of the animation, but a change to a fading effect.

doadam · 2023-11-03T22:14:50Z

I'm using hammerspoon for key binding, and had Opt+number to switch to a specific space. I have 2 displays and found a hacky workaround. The animation is still there and there are some sleeps, but at least I can navigate spaces now:
-- Function to get the active space ID and a table of visible spaces

function getSpaceInfo()
-- Execute the yabai command to fetch the JSON output
local yabaiOutput = hs.execute(yabai_path .. " -m query --spaces")
-- Decode the JSON output to a Lua table
local spaces, decodeError = hs.json.decode(yabaiOutput)
if not spaces then
    hs.printf("JSON decode err: %s", decodeError)
    return nil, nil
end
local focusedSpace = nil
local visibleSpaces = {}
-- Iterate through the spaces
for _, space in ipairs(spaces) do
    if space["has-focus"] == true then
        focusedSpace = space
    end
    if space["is-visible"] == true then
        table.insert(visibleSpaces, space)
    end
end
return focusedSpace, visibleSpaces
end

function focus_space_id(space_id)
yabai({"-m", "space", "--focus", '' .. space_id})
end

for k,v in pairs({'1', '2', '3', '4', '5', '6', '7', '8', '9', '10'}) do
hs.hotkey.bind({"alt"}, '' .. k % 10, function()
    local focusedSpace, visibleSpaces = getSpaceInfo()
    if focusedSpace then
        local targetDisplay = math.ceil(tonumber(k) / 5)
        local currentDisplay = focusedSpace.display
        --print("targetDisplay: ", targetDisplay)
        --print("currentDisplay: ", currentDisplay)
        if targetDisplay == currentDisplay then
            -- If the target and current display are the same, focus another space first
            for _, space in ipairs(visibleSpaces) do
                if space.display ~= currentDisplay then
                    --print("Focusing space ", space.index, " first")
                    focus_space_id(space.index)
                    hs.timer.doAfter(0.05, function()
                        focus_space_id(k)
                    end)
                    return
                end
            end
        end
        -- Focus the requested space
        focus_space_id(k)
    end
end)
end
FYI to get the current space you can use yabai -m query --spaces --space and to get the spaces on the current display you can do yabai -m query --displays --display | jq -c '.spaces'

You could get the next space up or down by doing yabai -m query --spaces --space | jq -c '.index + 1' / yabai -m query --spaces --space | jq -c '.index - 1' and you could check if that space is within your current display's list of spaces using something like if [ $(jq --null-input --argjson spaces "$SPACES" -c --argjson next_space "$NEXT_SPACE" '$next_space|IN($spaces[])') = "true" ]; then ... fi

All things I used to do when yabai was working for me :P

I prefer doing it with as few yabai calls as possible because each call has a slight overhead, which is noticeable if you switch spaces quickly :)

TuralAsgar · 2023-11-04T07:32:45Z

I'm using hammerspoon for key binding, and had Opt+number to switch to a specific space. I have 2 displays and found a hacky workaround. The animation is still there and there are some sleeps, but at least I can navigate spaces now:

-- Function to get the active space ID and a table of visible spaces
function getSpaceInfo()
    -- Execute the yabai command to fetch the JSON output
    local yabaiOutput = hs.execute(yabai_path .. " -m query --spaces")

    -- Decode the JSON output to a Lua table
    local spaces, decodeError = hs.json.decode(yabaiOutput)

    if not spaces then
        hs.printf("JSON decode err: %s", decodeError)
        return nil, nil
    end
    
    local focusedSpace = nil
    local visibleSpaces = {}
    
    -- Iterate through the spaces
    for _, space in ipairs(spaces) do
        if space["has-focus"] == true then
            focusedSpace = space
        end
        if space["is-visible"] == true then
            table.insert(visibleSpaces, space)
        end
    end

    return focusedSpace, visibleSpaces
end

function focus_space_id(space_id)
    yabai({"-m", "space", "--focus", '' .. space_id})
end

for k,v in pairs({'1', '2', '3', '4', '5', '6', '7', '8', '9', '10'}) do
    hs.hotkey.bind({"alt"}, '' .. k % 10, function()
        local focusedSpace, visibleSpaces = getSpaceInfo()

        if focusedSpace then
            local targetDisplay = math.ceil(tonumber(k) / 5)
            local currentDisplay = focusedSpace.display
            --print("targetDisplay: ", targetDisplay)
            --print("currentDisplay: ", currentDisplay)

            if targetDisplay == currentDisplay then
                -- If the target and current display are the same, focus another space first
                for _, space in ipairs(visibleSpaces) do
                    if space.display ~= currentDisplay then
                        --print("Focusing space ", space.index, " first")
                        focus_space_id(space.index)

                        hs.timer.doAfter(0.05, function()
                            focus_space_id(k)
                        end)

                        return
                    end
                end
            end

            -- Focus the requested space
            focus_space_id(k)
        end
    end)
end

I added this script and reloaded Hammerspoon but it didn't change space when I pressed opt+number.
Should I need other steps after adding and reloading?

doadam · 2023-11-04T11:13:54Z

I'm using hammerspoon for key binding, and had Opt+number to switch to a specific space. I have 2 displays and found a hacky workaround. The animation is still there and there are some sleeps, but at least I can navigate spaces now:

-- Function to get the active space ID and a table of visible spaces
function getSpaceInfo()
    -- Execute the yabai command to fetch the JSON output
    local yabaiOutput = hs.execute(yabai_path .. " -m query --spaces")

    -- Decode the JSON output to a Lua table
    local spaces, decodeError = hs.json.decode(yabaiOutput)

    if not spaces then
        hs.printf("JSON decode err: %s", decodeError)
        return nil, nil
    end
    
    local focusedSpace = nil
    local visibleSpaces = {}
    
    -- Iterate through the spaces
    for _, space in ipairs(spaces) do
        if space["has-focus"] == true then
            focusedSpace = space
        end
        if space["is-visible"] == true then
            table.insert(visibleSpaces, space)
        end
    end

    return focusedSpace, visibleSpaces
end

function focus_space_id(space_id)
    yabai({"-m", "space", "--focus", '' .. space_id})
end

for k,v in pairs({'1', '2', '3', '4', '5', '6', '7', '8', '9', '10'}) do
    hs.hotkey.bind({"alt"}, '' .. k % 10, function()
        local focusedSpace, visibleSpaces = getSpaceInfo()

        if focusedSpace then
            local targetDisplay = math.ceil(tonumber(k) / 5)
            local currentDisplay = focusedSpace.display
            --print("targetDisplay: ", targetDisplay)
            --print("currentDisplay: ", currentDisplay)

            if targetDisplay == currentDisplay then
                -- If the target and current display are the same, focus another space first
                for _, space in ipairs(visibleSpaces) do
                    if space.display ~= currentDisplay then
                        --print("Focusing space ", space.index, " first")
                        focus_space_id(space.index)

                        hs.timer.doAfter(0.05, function()
                            focus_space_id(k)
                        end)

                        return
                    end
                end
            end

            -- Focus the requested space
            focus_space_id(k)
        end
    end)
end

I added this script and reloaded Hammerspoon but it didn't change space when I pressed opt+number. Should I need other steps after adding and reloading?

You need some more functions/code:

local json = require("hs.json")

function init_brew(args)
    output, status, t, rc = hs.execute("brew --prefix", true)
    output = output:gsub("\n", "")
    return output
end

yabai_path = brew_path .. "/bin/yabai"
function yabai(args)
    --print("yabai args: ", hs.inspect(table.pack(args)))
    hs.task.new(yabai_path, nil, function(ud, ...)
        --print("stream", hs.inspect(table.pack(...)))
        return true
    end, args):start()
end

I also use the ReloadConfiguration spoon to auto load on every modification:

hs.loadSpoon("ReloadConfiguration")

The reason I created this yabai function is because most of the yabai commands are ok if they're asynchronous (querying the status isn't, hence the difference in getSpaceInfo) and this makes sure the UI doesn't get stuck if yabai doesn't run instantly.

brorbw · 2023-11-05T22:39:29Z

I have this "native" solution for finding spaces belonging to a display rather than hammerspoon.

readonly SPACE_INDEX=$1

readonly ACTIVE_DISPLAY_ID=$(yabai -m query --spaces |
	jq '.[] | select(."has-focus" == true).display')

readonly SPACES_OF_ACTIVE_DISPLAY=$(yabai -m query --displays |
	jq ".[] | select(.index == $ACTIVE_DISPLAY_ID).spaces")

readonly TARGET_SPACE=$(echo $SPACES_OF_ACTIVE_DISPLAY |
	jq -r ".[$SPACE_INDEX]")

yabai -m space --focus $TARGET_SPACE

brorbw · 2023-11-05T23:49:43Z

It could be a separate issue but it would seem that destroy and create does not work either

choodfire · 2023-11-09T15:34:18Z

Any updates on 14.1.1?

yuser1337 · 2023-11-10T08:21:12Z

Any updates on 14.1.1?

Its the same, doesn't work

suinly · 2023-11-12T18:40:31Z

Works in version 6.0.1! 🎉

choodfire · 2023-11-12T19:08:29Z

Thank you @koekeishiya!

frigaut · 2023-11-13T01:45:13Z

Yes, can confirm space focus etc work in 6.0.1. Thanks @koekeishiya

hb0nes · 2023-11-13T09:48:46Z

Can confirm here as well. Can we close this issue?

konstruktor227 · 2023-11-13T10:27:55Z

Everything working great again after latest update. Thanks @koekeishiya!

frigaut · 2023-11-14T01:12:39Z

Happiness is a fully functioning yabai :-)

davidandradeduarte · 2024-01-03T12:22:07Z

Just upgraded to Sonoma 14.2.1, and it stopped working again.
yabai doesn't focus any space and there's no error output.

Ignore. I needed to (again) give the necessary system permissions to yabai, after the upgrade.

koekeishiya closed this as completed Nov 13, 2023

Space focusing issues with Sonoma 14.1 (23B74) #1937

Space focusing issues with Sonoma 14.1 (23B74) #1937

Comments

doadam commented Oct 26, 2023

rwijtvliet commented Oct 26, 2023

doadam commented Oct 27, 2023

liuduwei commented Oct 27, 2023 • edited Loading

kabaliwths commented Oct 27, 2023

davidandradeduarte commented Oct 29, 2023

jakehamilton commented Oct 29, 2023

mescalas commented Oct 29, 2023

dvrkoo commented Oct 30, 2023

TuralAsgar commented Oct 30, 2023

denis-anashkin commented Oct 30, 2023

ccimponeriu1996 commented Oct 30, 2023

philipphoertnagl commented Oct 30, 2023 • edited Loading

simonemargio commented Oct 31, 2023 • edited Loading

hb0nes commented Oct 31, 2023

Rodion-Bozhenko commented Nov 1, 2023

kalamov commented Nov 1, 2023

rayjanoka commented Nov 1, 2023 • edited Loading

konstruktor227 commented Nov 2, 2023 • edited Loading

suinly commented Nov 2, 2023 • edited Loading

henrythor commented Nov 2, 2023 • edited Loading

doadam commented Nov 2, 2023 • edited Loading

henrythor commented Nov 3, 2023

suinly commented Nov 3, 2023

doadam commented Nov 3, 2023

TuralAsgar commented Nov 4, 2023

doadam commented Nov 4, 2023

brorbw commented Nov 5, 2023 • edited Loading

brorbw commented Nov 5, 2023

choodfire commented Nov 9, 2023

yuser1337 commented Nov 10, 2023

suinly commented Nov 12, 2023

choodfire commented Nov 12, 2023

frigaut commented Nov 13, 2023

hb0nes commented Nov 13, 2023

konstruktor227 commented Nov 13, 2023

frigaut commented Nov 14, 2023

davidandradeduarte commented Jan 3, 2024 • edited Loading

liuduwei commented Oct 27, 2023 •

edited

Loading

philipphoertnagl commented Oct 30, 2023 •

edited

Loading

simonemargio commented Oct 31, 2023 •

edited

Loading

rayjanoka commented Nov 1, 2023 •

edited

Loading

konstruktor227 commented Nov 2, 2023 •

edited

Loading

suinly commented Nov 2, 2023 •

edited

Loading

henrythor commented Nov 2, 2023 •

edited

Loading

doadam commented Nov 2, 2023 •

edited

Loading

brorbw commented Nov 5, 2023 •

edited

Loading

davidandradeduarte commented Jan 3, 2024 •

edited

Loading