macOS 14 Sonoma #1772

0xCUB3 · 2023-06-06T12:19:39Z

Yes, yes, it's the first day...

The good news is that yabai is functional. The bad news is that it randomly just stops working, restarts itself, works again, and the cycle continues. Sometimes when I try to start yabai manually, I get this error:

Bootstrap failed: 5: Input/output error
Try re-running the command as root for richer errors.
Error: Failure while executing; /bin/launchctl bootstrap gui/501 /Users/me/Library/LaunchAgents/homebrew.mxcl.yabai.plist exited with 5.

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

koekeishiya · 2023-06-06T12:21:24Z

Upgrade to yabai v5.0.6 and stop using brew services. There is a launchd interface directly in yabai now.

0xCUB3 · 2023-06-06T12:38:11Z

thank you! This works :)
Will close for now unless another issue occurs

pupbrained · 2023-06-06T13:14:25Z

@0xCUB3 have you had any issues with yabai segfaulting over and over? I did the same thing as mentioned (upgrading to yabai v5.0.6 and using yabai --install-service) but when starting the service it runs for about a minute, then segfaults. Looking at the logs it seems to be failing on:

yabai: could not access accessibility features! abort..

But I've tried removing yabai from accessibility, restarting the service, and adding it back when it asked for the permission, and that didn't change anything.

(Apologies if I shouldn't post this here, just using this as I'm having a similar issue.)

0xCUB3 · 2023-06-06T13:15:18Z

remove all other "yabai" instances from accessibility and then try again. Make sure yabai is on the latest version too.

pupbrained · 2023-06-06T13:21:38Z

I've made sure to remove all the other instances, and I'm using yabai from the latest GitHub release.

0xCUB3 · 2023-06-06T13:22:22Z

Interesting. I followed the same steps and had no issues. Someone else will have to chime in.

koekeishiya · 2023-06-06T13:23:13Z

You should keep in mind that Sonoma is in developer preview 1 and the issues you experience are likely macOS issues/bugs, that will be fixed in later previews. This is even more likely considering you seem to be having issues using the accessiblity API, which is a publicly documented and fairly stable API (stable as in Apple very rarely, if ever, does breaking changes to this API).

0xCUB3 · 2023-06-06T13:24:21Z

yeah that's correct; the issues will likely resolve themselves over time. I mostly upgraded to test my own apps to see if they work 🤪

pupbrained · 2023-06-06T13:25:08Z

You should keep in mind that Sonoma is in developer preview 1 and the issues you experience are likely macOS issues/bugs, that will be fixed in later previews. This is even more likely considering you seem to be having issues using the accessiblity API, which is a publicly documented and fairly stable API (stable as in Apple very rarely, if ever, does breaking changes to this API).

Yeah, that's most likely what's happening here. It's not too much of an issue, but I just wanted to see if it's happening to anybody else.

pupbrained · 2023-06-06T18:24:03Z

Okay, after trying a few more things, the segfault seems to be caused by focus_follows_mouse being set to autoraise?

After removing that line from my yabairc and re-running yabai, I've had it running for about 5 minutes now with no segfaults. Previously, it would immediately segfault when switching windows by moving the mouse to another window.

What I find especially odd, though, is that Amethyst's implementation of focus_follows_mouse works just fine, even with yabai running as the window manager and Amethyst being disabled.

EDIT:
I cloned the yabai repo to my mac, and tried debugging it through CLion. From what I can tell, the segfaults happen when yabai attempts to switch window focus with an EXC_BAD_ACCESS. According to CLion, the error traces back to this line:

yabai/src/window_manager.c

Line 1218 in fa966c7

SLPSPostEventRecordTo(window_psn, bytes1);

descensiontohell · 2023-06-07T12:21:52Z

It is not functional. It segfaults every focus switch. Gotta rollback the OS now

0xCUB3 · 2023-06-07T12:22:41Z

yes it started doing it for me again, even with the switch to the built-in launchd interface.

pupbrained · 2023-06-07T12:38:41Z

yes it started doing it for me again, even with the switch to the built-in launchd interface.

it seems to be either an issue with the focus-switching code, or how macOS Sonoma handles it.

ralphptorres · 2023-06-07T22:54:42Z

it seems to be either an issue with the focus-switching code, or how macOS Sonoma handles it.

I can confirm this. Other yabai window-specific commands like swap, warp, resize, toggle gap, and toggle zoom-fullscreen work without yabai crashing. Whereas executing the focus (and interestingly, toggle native-fullscreen) command and hovering to an unfocused window with the config focus_follows_mouse enabled make it crash.

koekeishiya · 2023-06-08T21:00:50Z

When yabai focuses a window it is a mix of private APIs, reverse engineered events that are sent directly to an application, and the AX API. This combination is necessary as a workaround to a problem where the wrong window will receive focus in a multi-monitor setup. See #102 for history. Window focusing has worked this way ever since yabai v1.0.6.

I don't know if this is broken in Sonoma, or if the crash that is observed now are happening because of issues that Apple will resolve in later versions of Sonoma, as they are still on the first developer beta.

I am personally not going to care much about issues that arise, until they ship the ~3rd public beta release.

pupbrained · 2023-06-22T00:02:50Z

Little update to this, 2nd beta seems to still be broken w/ yabai. It also seems they recently deprecated a lot of things, so it might have something to do with that?

UPDATE: I thought yabai had been working, but the bug still seems to be present.

pupbrained · 2023-07-09T23:56:18Z

Again, 3rd beta has the same issues. Seems that Apple most likely changed something with the APIs that yabai uses, considering I've also seen lots of API deprecation warnings in numerous apps.

i-jared · 2023-07-20T14:37:09Z

After upgrading I am unable to switch spaces focus. Anybody else experiencing this issue?

roelvangils · 2023-07-22T13:39:00Z

I'm fully aware that I don't deserve support as a Sonoma Public Beta user (sorry, I couldn't resist installing it), but maybe someone can help me out anyway! 😁

What I did: I uninstalled yabai with brew uninstall yabai after installing Sonoma Public Beta 1 because I thought it was a good idea to start over. Then I attempted to reinstall it, but that didn't work. First, Homebrew complains (for a good reason), but that's not the issue. It's this error message I'm stuck on:

Error: Your Xcode (14.3.1) is too outdated.
Please update to Xcode 15.0 (or delete it).

I did install Xcode 15 Beta (4), but I still get the message saying Xcode is outdated. Also, I'm unsure what does Yabai mean by "or delete it"? 🤔 Should I delete the Xcode 15 beta again? Not sure if that's going to help.

Full output:

==> Downloading https://formulae.brew.sh/api/formula.jws.json
############################################################################################################################################################################ 100.0%
==> Downloading https://formulae.brew.sh/api/cask.jws.json
############################################################################################################################################################################ 100.0%
Warning: You are using macOS 14.
We do not provide support for this pre-release version.
It is expected behaviour that some formulae will fail to build in this pre-release version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.

==> Fetching koekeishiya/formulae/yabai
==> Downloading https://github.com/koekeishiya/yabai/releases/download/v5.0.6/yabai-v5.0.6.tar.gz
==> Downloading from https://objects.githubusercontent.com/github-production-release-asset-2e65be/184909163/df79b725-6f01-431f-95de-a5911d7d66bc?X-Amz-Algorithm=AWS4-HMAC-SHA256&X
############################################################################################################################################################################ 100.0%
==> Installing yabai from koekeishiya/formulae
Error: Your Xcode (14.3.1) is too outdated.
Please update to Xcode 15.0 (or delete it).
Xcode can be updated from:
  https://developer.apple.com/download/all/

roelvangils · 2023-07-22T13:52:02Z

Update (to whom it concerns): after installing Xcode 15 Beta, you need to run this command:

sudo xcode-select --switch /Applications/Xcode-beta.app

This lets you install Yabai 5.0.6 again.

JacquesCherbuin · 2023-07-24T03:59:26Z

I switched to Sonoma, reinstalled yabai and switched to Xcode-beta. Window swap, warp, mirror, padding, rotate, toggle float, grid mode, toggle split and opacity all work as expected. However, focusing windows and spaces doesn't work. Focusing windows occasionally causes all windows to switch around randomly after about 3 seconds, and occasionally it will work a single time but not work after that. So for now I've gone back to Ventura... I hope you will be able to eventually figure out a fix, I couldn't use macOS without yabai - it's so good

dchou-zxy · 2023-07-24T15:30:36Z

I am also unable to switch spaces since switching to Sonoma beta:
yabai -m space --focus next
cannot focus space due to an error with the scripting-addition.

roelvangils · 2023-07-24T20:24:29Z

@JacquesCherbuin my experience is identical to yours.

I didn't switch back to Ventura (I think the only way is to restore from a Time Machine backup, and that would take forever and is not without risks). Besides, I like everything else in Sonoma too much. Yabai is the only third-party app that is causing me trouble 😁 But that was totally to be expected, of course. Nonetheless, I'm holding my breath for a Yabai update and I hope @koekeishiya won't let us wait until the final release! 🙊

f64u · 2023-07-25T00:41:13Z

I'm also experiencing the focusing issue. I hope this gets addressed :(

ditadi · 2023-07-25T11:15:02Z

Same issue here, every three seconds yabai "reset" and refocus.

With this, it is impossible to use Yabai, so I stopped the service and hope we have a fix soon to be used again.

koekeishiya · 2023-07-25T14:09:24Z

You can apply this patch to the master branch (ea4eb84) to make window focus work without segfaulting.
Note that this patch will likely reintroduce the issue mentioned in #102 (and focus without raise aka autofocus will not work).

diff --git a/src/window_manager.c b/src/window_manager.c
index c14309c..6a8d4c8 100644
--- a/src/window_manager.c
+++ b/src/window_manager.c
@@ -1221,6 +1221,11 @@ static void window_manager_make_key_window(ProcessSerialNumber *window_psn, uint
 
 void window_manager_focus_window_without_raise(ProcessSerialNumber *window_psn, uint32_t window_id)
 {
+    if (workspace_is_macos_sonoma()) {
+        debug("%s is not available on macOS Sonoma..\n", __FUNCTION__);
+        return;
+    }
+
     if (psn_equals(window_psn, &g_window_manager.focused_window_psn)) {
         uint8_t bytes1[0xf8] = { [0x04] = 0xf8, [0x08] = 0x0d, [0x8a] = 0x02 };
         memcpy(bytes1 + 0x3c, &g_window_manager.focused_window_id, sizeof(uint32_t));
@@ -1246,13 +1251,18 @@ void window_manager_focus_window_without_raise(ProcessSerialNumber *window_psn,
 
 void window_manager_focus_window_with_raise(ProcessSerialNumber *window_psn, uint32_t window_id, AXUIElementRef window_ref)
 {
+    if (workspace_is_macos_sonoma()) {
+        _SLPSSetFrontProcessWithOptions(window_psn, 0, kCPSNoWindows);
+        AXUIElementPerformAction(window_ref, kAXRaiseAction);
+    } else {
 #if 1
-    _SLPSSetFrontProcessWithOptions(window_psn, window_id, kCPSUserGenerated);
-    window_manager_make_key_window(window_psn, window_id);
-    AXUIElementPerformAction(window_ref, kAXRaiseAction);
+        _SLPSSetFrontProcessWithOptions(window_psn, window_id, kCPSUserGenerated);
+        window_manager_make_key_window(window_psn, window_id);
+        AXUIElementPerformAction(window_ref, kAXRaiseAction);
 #else
-    scripting_addition_focus_window(window_id);
+        scripting_addition_focus_window(window_id);
 #endif
+    }
 }
 
 #pragma clang diagnostic push

As I have mentioned before; if this software is critical to your workflow you should refrain from upgrading to a beta OS.

0xCUB3 · 2023-07-25T14:22:39Z

Perfect! For those of you who don't know how to apply this patch, you need to switch to the dev version of yabai, which runs off of the latest commit.

Link to Guide

As @koekeishiya mentioned, however, run this at your own risk and don't run beta versions of macOS unless you understand all of the risks involved

koekeishiya · 2023-10-10T19:27:28Z

I've already made up my mind. The current iteration of window borders will be removed.

gldtn · 2023-10-11T04:38:29Z

I personally love the window borders. Haven't noticed many issues with them, if any, but if it's for the best of the project, than it must be removed!

It will be missed /:

albert-ying · 2023-10-11T05:00:15Z

I've already made up my mind. The current iteration of window borders will be removed.

if the window borders are gone, does that mean the blur bg is gone as well?

tshu-w · 2023-10-11T10:36:48Z

Removing the window borders makes modal keymaps for skhdrc unusable (; https://gist.github.com/ryan-mooore/016b0d10e3dcc138e429570d0752fbad

gldtn · 2023-10-11T13:22:35Z

Removing the window borders makes modal keymaps for skhdrc unusable (; https://gist.github.com/ryan-mooore/016b0d10e3dcc138e429570d0752fbad

Probably because of these lines on that config:

:: default  : yabai -m config active_window_border_color 0xff61afef
:: focus  @ : yabai -m config active_window_border_color 0xffe06c75  # Focus window, desktop, monitors
:: grid   @ : yabai -m config active_window_border_color 0xff56b6c2  # Floating window layout
:: swap   @ : yabai -m config active_window_border_color 0xffc678dd  # Swap windows
:: warp   @ : yabai -m config active_window_border_color 0xffe5c07b  # Warp and send to desktop/monitors
:: warpnf @ : yabai -m config active_window_border_color 0xffd19a66  # Same, but don't follow focus
:: resize @ : yabai -m config active_window_border_color 0xff98c379  # Resize window operations

Comment those out and see if it works. You most likely will need to remove:

default
focus
grid
swap
warp
warpnf
resize

From the end of the commands where it ends with those, i.e ; focus as it seems it's referencing to the borders that is no longer there and thus giving you errors. Also remove anything that references active_window_border_color, again this is no longer in yabai!

This is the first time I saw a config like this and will try it when I get home as I found it interesting.

tshu-w · 2023-10-11T13:59:32Z

Probably because of these lines on that config:

Yes, I know. I'm just expressing my nostalgia for the window border. I may need to install Hammerspoon or something else to achieve indication.

Modal keymaps are difficult to use without an indicator.

gldtn · 2023-10-11T14:49:10Z

Very true, I updated yesterday and I did notice great improvement though without the borders. I turned windows opacity on to minimal just to get some kind of indication, I'm also using the window control buttons from mac as my indicator of what windows is active for now. Guess is something I'll have to see how well I adapt to it.

hbthen3rd · 2023-10-12T10:08:30Z

I totally understand the decision. And I appreciate the work you're doing it. But damn, I'd be lying if I say I don't miss the border. I do notice the performance gain, but like 87% of my RICE aesthetic is gone now due the lack of window borders. Also, it's hard to know which window has the focus since I try to hide titlebar whenever I can (iTerms, Firefox, VSCode, Neovide).

robrecord · 2023-10-13T10:08:56Z

Modal keymaps are difficult to use without an indicator.

Something in SketchyBar might help us here https://github.com/FelixKratz/SketchyBar

VentusTWY · 2023-10-17T16:34:53Z

having the same problem here on MacOS 14.0 Sonoma , yabai stopping randomly from time to time
on yabai 6.0 - mainly using it for config focus_follows_mouse autofocus

aserranoni · 2023-10-20T00:10:52Z

Hey guys, I also was an avid user of window borders before this update, yesterday I made a small workaround to make sketchybar display the current skhd current mode (that was previously done by the window border colors). If anybody wants to take a similar approach, here is a gist.

smithshelke · 2023-10-31T04:59:43Z

having the same problem here on MacOS 14.0 Sonoma , yabai stopping randomly from time to time on yabai 6.0 - mainly using it for config focus_follows_mouse autofocus

yep same here, switching desktops is not working for me. Although maximizing panes or swapping their positions is working.

chrisgrovers · 2023-11-02T15:48:26Z

having the same problem here on MacOS 14.0 Sonoma , yabai stopping randomly from time to time on yabai 6.0 - mainly using it for config focus_follows_mouse autofocus

yep same here, switching desktops is not working for me. Although maximizing panes or swapping their positions is working.

Adding on to say I'm also experiencing issues where yabai randomly stops. I'll run yabai --start-service and after everything finds its place (I might be able to move focus with SKHD) yabai crashes. After an arbitrary amount of time (5-10 seconds), if my focus is on a different window, yabai starts up again and shifts around windows only to start the crash cycle all over again.

This issue does not happen when I run yabai. Everything (mostly) works as expected without running --start-service.

err.log, and out.log don't show any helpful information AFAICT

yabai -v: yabai-v6.0.0
macOS version: 14.1 (23B74)

output of `/tmp/yabai_$USER.out.log`

Pretty much all my settings, and resize events done at startup

EVENT_HANDLER_DAEMON_MESSAGE: config layout bsp
EVENT_HANDLER_WINDOW_TITLE_CHANGED: iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: iTerm2 176
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED:DEBOUNCED iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 108
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 108
EVENT_HANDLER_WINDOW_RESIZED:DEBOUNCED Google Chrome 108
EVENT_HANDLER_WINDOW_RESIZED: Firefox 226
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Firefox 226
EVENT_HANDLER_WINDOW_RESIZED:DEBOUNCED Firefox 226
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 2368
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 2368
EVENT_HANDLER_DAEMON_MESSAGE: config mouse_follows_focus on
EVENT_HANDLER_WINDOW_RESIZED:DEBOUNCED Google Chrome 2368
EVENT_HANDLER_DAEMON_MESSAGE: config focus_follows_mouse autofocus
EVENT_HANDLER_DAEMON_MESSAGE: space 1 --label one
EVENT_HANDLER_DAEMON_MESSAGE: space 2 --label two
EVENT_HANDLER_DAEMON_MESSAGE: space 3 --label three
EVENT_HANDLER_DAEMON_MESSAGE: space 4 --label four
EVENT_HANDLER_DAEMON_MESSAGE: space 5 --label five
EVENT_HANDLER_DAEMON_MESSAGE: space 6 --label six
EVENT_HANDLER_DAEMON_MESSAGE: space 9 --label nine
EVENT_HANDLER_DAEMON_MESSAGE: config top_padding 5
EVENT_HANDLER_WINDOW_RESIZED: iTerm2 176
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 108
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 108
EVENT_HANDLER_WINDOW_RESIZED: Firefox 226
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Firefox 226
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 2368
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 2368
EVENT_HANDLER_DAEMON_MESSAGE: config bottom_padding 5
EVENT_HANDLER_WINDOW_TITLE_CHANGED: iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 108
EVENT_HANDLER_WINDOW_RESIZED: Firefox 226
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 2368
EVENT_HANDLER_DAEMON_MESSAGE: config left_padding 5
EVENT_HANDLER_WINDOW_TITLE_CHANGED: iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: iTerm2 176
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 108
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 108
EVENT_HANDLER_WINDOW_RESIZED: Firefox 226
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Firefox 226
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 2368
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 2368
EVENT_HANDLER_DAEMON_MESSAGE: config right_padding 5
EVENT_HANDLER_WINDOW_RESIZED: iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 108
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 108
EVENT_HANDLER_WINDOW_RESIZED: Firefox 226
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 2368
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 2368
EVENT_HANDLER_DAEMON_MESSAGE: config window_gap 5
EVENT_HANDLER_WINDOW_RESIZED: iTerm2 176
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 108
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 108
EVENT_HANDLER_WINDOW_RESIZED: Firefox 226
EVENT_HANDLER_WINDOW_RESIZED: Google Chrome 2368
EVENT_HANDLER_WINDOW_MOVED:DEBOUNCED Google Chrome 2368
EVENT_HANDLER_DAEMON_MESSAGE: rule --add app=^System Information$ manage=off
EVENT_HANDLER_DAEMON_MESSAGE: rule --add app=^System Preferences$ manage=off
EVENT_HANDLER_DAEMON_MESSAGE: rule --add app=^System Settings$ manage=off
EVENT_HANDLER_DAEMON_MESSAGE: rule --add title=Preferences$ manage=off
EVENT_HANDLER_DAEMON_MESSAGE: rule --add title=^BetterTouchTool manage=off
EVENT_HANDLER_DAEMON_MESSAGE: rule --add title=Settings$ manage=off

^^^ This is basically the repeated

output of `/tmp/yabai_$USER.err.log`

``` could not locate the space to act on! could not locate the space to act on! could not locate the space to act on! could not locate the space to act on! ```

yabairc

yabai -m config debug_output on

yabai -m config layout bsp

# global settings
yabai -m config mouse_follows_focus          on
yabai -m config focus_follows_mouse          autofocus

# Monitor/Spaces setup
yabai -m space 1 --label one
yabai -m space 2 --label two
yabai -m space 3 --label three
yabai -m space 4 --label four
yabai -m space 5 --label five
yabai -m space 6 --label six
yabai -m space 9 --label nine

# Set all padding and gaps to 5pt (default: 0)
yabai -m config top_padding    5
yabai -m config bottom_padding 5
yabai -m config left_padding   5
yabai -m config right_padding  5
yabai -m config window_gap     5

# float system preferences
yabai -m rule --add app='^System Information$' manage=off
yabai -m rule --add app='^System Preferences$' manage=off
yabai -m rule --add app='^System Settings$' manage=off
yabai -m rule --add title='Preferences$' manage=off

# float Better Touch Tool Preference window
yabai -m rule --add title='^BetterTouchTool' manage=off

# float g settings
# yabai -m rule --add title='^'

# float settings windows
yabai -m rule --add title='Settings$' manage=off

Edits: Adding details - macos version, yabai version, yabairc

HudonMatis · 2023-11-11T18:30:35Z

yabai -m space --focus 1

Does it work for you guys in version 6.0.0 ? I can't seem to make it work.
When I do this command in the terminal nothing happens. When on the same space I get as expected
cannot focus an already focused space.
I have the following config:
M2 Pro macbook, Mac OS Sonoma (Version 14.1.1 (23B81)), yabai 6.0.0, reinstalled scripting-addtions, as instructed, added yabai to accessibility, even rebooted.

Am I missing somthing to make it work ? @codekcv @gldtn @saurabhsharan @diocletiann @ZirixCZ @frigaut @0xCUB3

Big thanks to all yabai contributors.

HudonMatis · 2023-11-12T11:02:44Z

yabai -m space --focus 1

Does it work for you guys in version 6.0.0 ? I can't seem to make it work. When I do this command in the terminal nothing happens. When on the same space I get as expected cannot focus an already focused space. I have the following config: M2 Pro macbook, Mac OS Sonoma (Version 14.1.1 (23B81)), yabai 6.0.0, reinstalled scripting-addtions, as instructed, added yabai to accessibility, even rebooted.

Am I missing somthing to make it work ? @codekcv @gldtn @saurabhsharan @diocletiann @ZirixCZ @frigaut @0xCUB3

Big thanks to all yabai contributors.

From HEAD now everything seems to work fine !

devnoname120 · 2023-11-22T22:27:04Z

Can someone else confirm that everything works properly on Sonoma when using HEAD?

frigaut · 2023-11-22T23:24:06Z

Yes, for me everything works on Sonoma as before.

devnoname120 · 2023-11-23T00:21:09Z

@frigaut Do you use yabai with SIP disabled + scripting additions? I'm especially interested/concerned about instant virtual spaces switching.

frigaut · 2023-11-23T01:16:17Z

@devnoname120 yes, I use yabai with SIP disabled + scripting addition, and "instant" space switching is working fine.

gldtn · 2023-11-23T01:32:39Z

@frigaut

Yes, space switching has been working on Sonoma 14.1.1 w/ Yabai 6.0.1 HEAD

If you want to do a quick update you can try my lil script out here: #1904 (comment)

This keeps me from having to go to the wiki every time I want to update Yabai, and it takes care of all the scripting addition reconfiguration.

loonalol · 2023-11-27T01:21:44Z

is space switching working on sonoma 14.2 Beta3?

frigaut · 2023-11-27T01:37:02Z

I suppose you mean 14.2 beta 3?

loonalol · 2023-11-27T02:10:14Z

I suppose you mean 14.2 beta 3?

yep sorry about that 😆

koekeishiya · 2023-11-30T20:54:43Z

Works fine on 14.1.2.
14.2 will be added when it is out of beta.

SzymonMielecki · 2023-12-12T18:35:48Z

No output on yabai -m space --focus 2 but the space doesnt switch

❯ yabai -v
yabai-v6.0.1

❯ csrutil status
System Integrity Protection status: disabled.

just updated to sonoma 14.2 today

roelvangils · 2023-12-12T19:52:43Z

Works fine on 14.1.2. 14.2 will be added when it is out of beta.

The public release of 14.2 is just around the corner now! @koekeishiya, does this mean that a fix for 14.2 is ready and tested on RC2, and you're waiting for the public release to unleash it? 😉

SzymonMielecki · 2023-12-12T21:52:38Z

Works fine on 14.1.2. 14.2 will be added when it is out of beta.

The public release of 14.2 is just around the corner now! @koekeishiya, does this mean that a fix for 14.2 is ready and tested on RC2, and you're waiting for the public release to unleash it? 😉

aint it already out tho? i got it without beta enabled

roelvangils · 2023-12-12T23:30:26Z

aint it already out tho? i got it without beta enabled

You're correct; macOS 14.2 was publicly released two days ago. I was using the latest beta (Release Candidate 2) prior to that, but it has the same build number (23C64) as the public release, so there was no update on my end.

Now, we're having a partially broken situation with Yabai again. This is expected due to the nature of the application, but I'm hopeful that @koekeishiya will provide us with an update soon to make his users happy once again! 🙂

diocletiann · 2024-01-07T22:32:14Z

@diocletiann

FYI, it seems Sonoma introduced a really annoying behavior where if you quit the last window in a space, it automatically switches to the previously focused space. I was hoping Yabai could kill this "feature", I can't find any toggles for it the OS.

I don't have this happening to me. The setting "When switching to an application, switch to a Space with open windows for the application" is enabled.

I found the root cause. It was defaults write com.apple.finder QuitMenuItem -bool YES. If finder is not running, the OS will focus the previous app/window.

0xCUB3 closed this as completed Jun 6, 2023

0xCUB3 reopened this Jun 6, 2023

koekeishiya added a commit that referenced this issue Jul 25, 2023

#1772 generate macOS version checking functions

ea4eb84

koekeishiya unpinned this issue Dec 6, 2023

macOS 14 Sonoma #1772

macOS 14 Sonoma #1772

Comments

0xCUB3 commented Jun 6, 2023

koekeishiya commented Jun 6, 2023

0xCUB3 commented Jun 6, 2023

pupbrained commented Jun 6, 2023

0xCUB3 commented Jun 6, 2023

pupbrained commented Jun 6, 2023

0xCUB3 commented Jun 6, 2023

koekeishiya commented Jun 6, 2023 • edited Loading

0xCUB3 commented Jun 6, 2023

pupbrained commented Jun 6, 2023

pupbrained commented Jun 6, 2023 • edited Loading

descensiontohell commented Jun 7, 2023 • edited Loading

0xCUB3 commented Jun 7, 2023

pupbrained commented Jun 7, 2023

ralphptorres commented Jun 7, 2023

koekeishiya commented Jun 8, 2023 • edited Loading

pupbrained commented Jun 22, 2023 • edited Loading

pupbrained commented Jul 9, 2023

i-jared commented Jul 20, 2023

roelvangils commented Jul 22, 2023 • edited Loading

roelvangils commented Jul 22, 2023 • edited Loading

JacquesCherbuin commented Jul 24, 2023

dchou-zxy commented Jul 24, 2023

roelvangils commented Jul 24, 2023 • edited Loading

f64u commented Jul 25, 2023

ditadi commented Jul 25, 2023

koekeishiya commented Jul 25, 2023 • edited Loading

0xCUB3 commented Jul 25, 2023 • edited Loading

koekeishiya commented Oct 10, 2023

gldtn commented Oct 11, 2023

albert-ying commented Oct 11, 2023

tshu-w commented Oct 11, 2023

gldtn commented Oct 11, 2023 • edited Loading

tshu-w commented Oct 11, 2023

gldtn commented Oct 11, 2023 • edited Loading

hbthen3rd commented Oct 12, 2023

robrecord commented Oct 13, 2023

VentusTWY commented Oct 17, 2023

aserranoni commented Oct 20, 2023

smithshelke commented Oct 31, 2023 • edited Loading

chrisgrovers commented Nov 2, 2023 • edited Loading

HudonMatis commented Nov 11, 2023 • edited Loading

HudonMatis commented Nov 12, 2023 • edited Loading

devnoname120 commented Nov 22, 2023

frigaut commented Nov 22, 2023

devnoname120 commented Nov 23, 2023

frigaut commented Nov 23, 2023

gldtn commented Nov 23, 2023 • edited Loading

loonalol commented Nov 27, 2023 • edited Loading

frigaut commented Nov 27, 2023

loonalol commented Nov 27, 2023

koekeishiya commented Nov 30, 2023

SzymonMielecki commented Dec 12, 2023 • edited Loading

roelvangils commented Dec 12, 2023 • edited Loading

SzymonMielecki commented Dec 12, 2023

roelvangils commented Dec 12, 2023 • edited Loading

diocletiann commented Jan 7, 2024

koekeishiya commented Jun 6, 2023 •

edited

Loading

pupbrained commented Jun 6, 2023 •

edited

Loading

descensiontohell commented Jun 7, 2023 •

edited

Loading

koekeishiya commented Jun 8, 2023 •

edited

Loading

pupbrained commented Jun 22, 2023 •

edited

Loading

roelvangils commented Jul 22, 2023 •

edited

Loading

roelvangils commented Jul 22, 2023 •

edited

Loading

roelvangils commented Jul 24, 2023 •

edited

Loading

koekeishiya commented Jul 25, 2023 •

edited

Loading

0xCUB3 commented Jul 25, 2023 •

edited

Loading

gldtn commented Oct 11, 2023 •

edited

Loading

gldtn commented Oct 11, 2023 •

edited

Loading

smithshelke commented Oct 31, 2023 •

edited

Loading

chrisgrovers commented Nov 2, 2023 •

edited

Loading

HudonMatis commented Nov 11, 2023 •

edited

Loading

HudonMatis commented Nov 12, 2023 •

edited

Loading

gldtn commented Nov 23, 2023 •

edited

Loading

loonalol commented Nov 27, 2023 •

edited

Loading

SzymonMielecki commented Dec 12, 2023 •

edited

Loading

roelvangils commented Dec 12, 2023 •

edited

Loading

roelvangils commented Dec 12, 2023 •

edited

Loading