Repeated warnings about $USER being unset

[dominiklohmann]

When running via launchd (through brew services), yabai sometimes prints messages about being unable to get $USER. Running env -v shows that it is set, though. The socket files are also created properly with my username in them, so I'm really not sure what's happening. yabai does not abort when printing the message.

The screenshot below shows my testing setup. Note that this is with almost no other configuration, so there's no custom settings for launchd at all.

[koekeishiya]

That is likely an error when trying to send a message, not from the running instance of yabai. See https://github.com/koekeishiya/yabai/blob/master/src/yabai.c#L53

Edit: Just re-read your post. Probably not related to what I said as you were running through brew services.

[dominiklohmann]

For what it's worth, the message being printed is still prefixed with yabai: and not yabai-msg:. It also happens without any user interaction (no keypresses, no mouse movement, no applications open other than iTerm2 with tail -f /path/to/log), so I'm really unsure what's happening here.

[koekeishiya]

The message you get is only printed during startup of the actual persistent instance, so it would appear that something on your system tries to launch an instance of yabai at least.

_{Sent with GitHawk}

[dominiklohmann]

The issue still occured after I ran brew services stop yabai, so you were definitely right about something on my system trying to launch yabai.

I think brew services or launchd went wrong somewhere and duplicated the launch services entry (or at least loaded it in a faulty state, which persisted reboots). Running sudo launchctl remove homebrew.mxcl.yabai fixed the issue for me.