Goose application doesn't show anything on MacOS

[vidurvij-apptronik]

No description provided.

[blackgirlbytes]

@vidurvij-apptronik can you expand on your issue? What does it show? What steps did you take to reproduce? Thanks!

[michaelneale]

this may be due to lack of intel support for now: #876

[liflovs]

have same issue, apple silicon chip

Just launching after install is not triggering any windows

[michaelneale]

@liflovs can you look in ~/Library/Application Support/Goose/logs/main.log and look for errors?

[liflovs]

@michaelneale Goose dir is empty

[michaelneale]

ok I would suggest removing the app - and ~/.config/goose - and reinstall (newer version should be available)

[vidurvij-apptronik]

So. I downloaded the new application. When I run it, the dock shows that application is running but no window is produced.

[esaddag]

I have also same problem with an apple silicon chip macbook. When i checked logs i saw following error:

[error] goosed stderr for port 55075 and dir /Users/myuser: Error: Failed to create log directory

Caused by:
    Permission denied (os error 13)

[michaelneale]

@esaddag oh interesting that was in the Goose dir in application support? This looks like permissions on the app (perhaps more locked down machines?) - I would try running from source or the cli in that case

[esaddag]

@esaddag oh interesting that was in the Goose dir in application support? This looks like permissions on the app (perhaps more locked down machines?) - I would try running from source or the cli in that case

@michaelneale I tried cli but got a similar error:

Configuring Goose

thread 'main' panicked at crates/goose/src/config/base.rs:106:46:
Failed to create config directory: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I’m new to macOS, so there might be something I need to configure, but I haven’t encountered a similar error with other installations or apps.

[baxen]

Hey team! This happens if you have a ~/.config file that is not writable. Make sure you have read/write access, by running something like

mkdir -p ~/.config
chmod u+rw ~/.config

shoutout to kingmoonwalker from our discord for finding this

[nicolenadine]

permissions for ~/.config doesn't fix the issue for Desktop or CLI versions on my M2 MacBook Air. I already had read/write access set and it still doesn't open any windows when I launch the desktop version and I get the permission denied OS error 13 still when attempting to start a session in CLI. I've done a fresh install of both.