Replies: 4 comments
-
Sounds like your /etc/sudoer file may not been configured correctly or it has not been loaded with yabairc Run
And make sure it matches the output of:
If not, Copy the output of the echo command above to the Also I know you said you did this, but triple check these are the exact lines at the top of yabairc:
Finally restart yabai.. not sure if it actually requires a computer restart! |
Beta Was this translation helpful? Give feedback.
-
I've been running Yabai for some time now, and also I just updated to Sonoma without any problems at all. If you do run into problems with updates, you can always enable SIP again, update MacOS and disable it again! |
Beta Was this translation helpful? Give feedback.
-
On last thing, which version of MacOS are you on? I'm assuming your running Intel based system with the command above! If your on APPLE SILICON, you need to use the correct SIP command depending on the version of you MacOS. |
Beta Was this translation helpful? Give feedback.
-
Thanks for all the answers @gldtn . It's been a while that I posted this, and I also posted this as an "issue" in the repo, and my issue was resolved, so, at least for now, things to be working fine EDIT: since my issue, as I mentioned, is resolved, I'm gonna close the discussion |
Beta Was this translation helpful? Give feedback.
-
So, I finally decied to give SIP and scripting addition a shot (main driver: to be able to work with spaces).
I disabled SIP with this command from the Wiki
First question: when running this, it warns me about:
which is scary, and I thin it implies that there's the possibility of me updating the OS and my Mac dying and not be usable, is that the case?
Other than that, with SIP being disabled, I followed instructions from the Wiki to install scripting additions:
sudoer
fileyabairc
with the linesBut when I run a space-focus command; e.g.
yabai -m space --focus 2
, I get:which is the exact error I get before disabling SIP and other steps.
I tried running
sudo yabai --install-sa
and the command runs, but I don't think anything happens because I still get the same error.It goes without saying that I have restarted yabai using
yabai --restart-service
multiple times, but nothing changedBeta Was this translation helpful? Give feedback.
All reactions