macOS Monterey and Apple Silicon #1054
Comments
koekeishiya
added
the
addressed on master; not released
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
I just installed it on an intel machine running Monterey 12.1 (SIP disabled). When connecting my computer to an external monitor it kept disconnecting and reconnecting. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@SamHep0803 yeah, sorry, I felt my comment wasn't fully correct and was missing a lot. I decided to remove it so I didn't cause any confusion. But it seems other are having trouble so I'll try and recreate my steps. These are in no way official steps, just what worked for me.
|
This comment has been minimized.
This comment has been minimized.
|
Just got the following crash today: |
This comment has been minimized.
This comment has been minimized.
Yep, I believe it was |
|
I noticed that sometimes when emacs is focused, changing spaces doesn't focus the front most app:
Actually now that I write this app, Safari seems to be the only culripit. |
|
closing as v4.0.0 is released; seems fairly stable as far as I can tell. |
koekeishiya
removed
the
addressed on master; not released
|
I'm still having issues, even after following @Tweoss steps I get this error: File Commands: Console.app logs: Any ideas? |
|
Hello, is it safe to update to Monterey 12.3.1? |
|
yes the latest release supports Monterey 12.3.1 |
|
Hi @koekeishiya , thanks for the awesome work. The new version of Mac OS Monterey 12.4 is available. Curious to know, is Yabai stable on the new version? |
|
Yep, Monterey 12.4 works fine. |
bump |
|
@mrchoc I've got the same hardware (MacBook Air, M1) running 12.3 and it's working fine for me. Maybe have another go at it from the top? |
Okay yabai mostly works now, but for some apps(safari, vscode) they dont seem to respond to |
|
Does |
It does. Quick switching is one of the highlights for me. |
I managed to find the issue, nothing wrong with yabai. It was karabiner elements messing with the keybinds. So if you encounter a similar issue and use karabiner, try disabling a few complex keybinds. |
Closed
|
I am still having the issue of the scripting addition not functioning on macOS 13. The command 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
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.And my boot arguments, as found by boot-args -arm64e_preview_abiYabai has accessibility permissions. Yabai is functioning in other ways, which leads me to believe it's just the scripting extension not loading completely. My sudoers file is set up properly, I've checked it a hundred times and remade it too. Some functionality that is working is bsp tiling, padding, disabling shadows (!! doesn't this require the scripting addition?), and gaps. I'm using skhd for hotkeys, but I've also tested the yabai -m space --focus commands on the command line directly, and they execute without error but don't do anything, so I'm sure it's a yabai issue. |
|
I am also having an issue with the scripting addition on macOS Ventura. My SIP is completely disabled, and my boot args are: However, for me, most things work except for window opacity ( from what I see ) |
This was referenced Mar 2, 2024
|
Same here: #!/usr/bin/env bash
sudo yabai -m --load-sa
yabai -m space --focus 2Output: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
The previous issues (#923, #725) contain a lot of noise and irrelevant information so I am making this one instead.
You can use the pre-built version I have attached to this post or clone the repository and build from source. To build a universal binary from source, simply run:
make cleanfollowed bymakefor debug build ormake installfor an optimised build. See the following wiki links for more detailed instructions:SIP instructions: from the wiki
Installation instructions: from the wiki
Pre-built version (with debug symbols) of commit (91a42e7): yabai-v4.0.0.tar.gz
NOTE: v4.0.0 is a breaking release and your config and related scripts need to be updated to reflect these changes.
See the updated docs and changelog
The yabai binary is built as a universal binary containing two images:
arm64andx86-64.The scripting-addition is built as a universal binary containing two images:
arm64eandx86-64.I am using Xcode v13.1 (13A1030d) (not command line tools) and Apple clang version 13.0.0 (clang-1300.0.29.3) on macOS Big Sur 11.6.1 (Intel) and macOS Monterey 12.1.0 (Apple Silicon). This commit has been tested and verified on Apple Silicon macOS 12.0.0, Apple Silicon macOS 12.0.1, Apple Silicon macOS 12.1.0 and Intel macOS 11.6.1.
To verify that your installed version conforms to the above, and is built correctly, run the following commands.
(Ignore the scripting-addition if you are not using it; running with SIP enabled):
This is what it should look like:
Debug loading of the scripting-addition:
Stop yabai and pkill Dock, then delete the temp files for yabai:
/tmp/yabai*Look for logs in
Console.app. Select your device on the left, and filter for "Dock" at the right, as shown in the below screenshot. Make sure no previous injection of the scripting-addition has been attempted; runpkill Dockfirst if it has. Clear the log window first for less noise, then runsudo yabai --load-saand assuming it returns no error, you should see something like the following:Known issues:
Window borders are broken; they cause random applications to freeze and also sometimes crashes the WindowServer. I have not found a pattern to this behaviour. Most likely borders will be disabled for Monterey until a solution is found. Limelight needs to be updated for Monterey; I'll look into that at some point, but no ETA.New window borders work differently and will work with SIP enabled.The API used to detect the height of the menubar is not working on Apple Silicon (but works when running the x86_64 version through Rosetta). The height cannot be hardcoded in Monterey, as the height changes depending on the selected display resolution.Fixed on master and in the pre-built version linked above.The function
display_manager_display_is_animating(uint32_t did)used for validating that the system is in a state where changes to spaces are appropriate to perform, is broken in Monterey. This could also have implications for integration with fullscreen application transitions.FAQ:
To run this command you first need to disable SIP, and reboot. Run the command as the root user, and reboot again.
This should be described in the wiki link referenced above.
This error is displayed when there is an architecture mismatch upon loading the scripting-addition. Verify the architecture as described above, using the
filecommand.Check the snippet explaining how to debug loading of the scripting-addition above.
--
Please read the above carefully before posting a comment; I'd like this to be somewhat readable and easy to follow.
If you have a problem that is not described above, feel free to post a comment with as much relevant information as possible:
Intel or Apple Silicon MacBook.
Which macOS version are you on.
What is the output of:
csrutil statusFor Apple Silicon, is arm64e enabled:
nvram -p | grep boot-argsWhich Xcode version are you using.
Which clang version are you using.
Output/result of the various debugging mentioned in the steps earlier in this post.
The text was updated successfully, but these errors were encountered: