Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MAC] Cannot open a directory from within the Application #326

Closed
EXT-OWL opened this issue Dec 30, 2024 · 11 comments
Closed

[MAC] Cannot open a directory from within the Application #326

EXT-OWL opened this issue Dec 30, 2024 · 11 comments
Assignees
Labels
bug Something isn't working

Comments

@EXT-OWL
Copy link

EXT-OWL commented Dec 30, 2024

I'm on MacOS Sequoia 15.1.1.

When I select 'Open Directory' from the menu I always get an error saying 'ERROR: [FILENAME] does not exist or does not have read permissions'

Attaching a Screenshot -
Screenshot from CleanShot-CleanShot on 30-12-2024@2x

I get the same error when I try dropping in a folder.

I can open a single image (drag and drop as well) but the issue seems to be only with trying to open directories.

I have used gatekeeper to unlock the app, and I've also given full disk access.

Any help would be appreciated.

@EXT-OWL EXT-OWL added the bug Something isn't working label Dec 30, 2024
@EXT-OWL EXT-OWL changed the title Cannot open a directory from within the Application [MAC] Cannot open a directory from within the Application Dec 30, 2024
@ggarra13
Copy link
Owner

I confirm the bug. A fix is coming...

@ggarra13
Copy link
Owner

@EXT-OWL
Copy link
Author

EXT-OWL commented Jan 1, 2025

Thank you.

I can confirm the second link fixes the issue, but it keeps crashing a bit.

The first link crashes while opening.

@ggarra13
Copy link
Owner

ggarra13 commented Jan 1, 2025

Can you post out the crashing logs that macOS generates when it crashes?
Both for the amd64 and for the arm64 ones?

@EXT-OWL
Copy link
Author

EXT-OWL commented Jan 6, 2025

Sure.

This the log for amd64 - https://pastebin.com/uvMk0fSs

Surprisingly I hvaen't been able to replicate a crash in the arm64 version. When I do I'll paste the logs here

@ggarra13
Copy link
Owner

ggarra13 commented Jan 6, 2025

Here should be a fixed version of amd64:

https://mega.nz/file/DCwxXZjK#JXSiqz2d4UlvdZ5ZjYoUfgBpgQmxKm7UL1sZHtZYBrA

However, since you are on arm64 machine, you probably should keep using that one, except for the OTIO bug reported on #238.

@EXT-OWL
Copy link
Author

EXT-OWL commented Jan 6, 2025

This is pretty embarrassing - I am very new to Mac and I didn't know the amd version wouldn't work on my arm machine :D. I will keep using this version that you shared. Looking forward to the updates !!

@ggarra13
Copy link
Owner

ggarra13 commented Jan 6, 2025

This is pretty embarrassing - I am very new to Mac and I didn't know the amd version wouldn't work on my arm machine :D.

Actually, the amd64 version can run on arm64 (M1, M2, M3,etc.) machines. It will run under an emulator called Rossetta2. That means it should run a tad slower, but it will work. The reason it was not working before was that it was missing a library that was installed on my machine but not on yours. Please give it a try to see that it actually boots.

@EXT-OWL
Copy link
Author

EXT-OWL commented Jan 8, 2025

Hi I can say that the amd64 version doesn't boot. it defaults to crash every time I open it. I can check it with the specific library that you mentioned - can you point me where to install it?

@ggarra13
Copy link
Owner

ggarra13 commented Jan 8, 2025

It cannot tell you what library is the problem without a crash log. First, try this version and see if it crashes:

.amd64:
https://mega.nz/file/ybAFyBJY#OOMxicWmmB51ErmuqC83_p2ezfCZHUUGXXzp9StRLQQ

If it still crashes, send me the crash log. I think then a new security feature of macOS that was updated in the New Year might be the problem.

@EXT-OWL
Copy link
Author

EXT-OWL commented Jan 13, 2025

.amd64: https://mega.nz/file/ybAFyBJY#OOMxicWmmB51ErmuqC83_p2ezfCZHUUGXXzp9StRLQQ

Happy to say that this version doesn't crash, and I can open directories without the error message popping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants