Logseq Locksup on MacOS Sonoma 14

[clickbrain]

Search first

• [X] I searched and no similar issues were found

What Happened?

Wanted to notify you guys that the only software I have that won't run on MacOS 17 Sonoma Beta is Logseq.

When I start Logseq I get the message that software is being verified Then I get a spinning beach ball Waited quite awhile, but then had to force quit I tried reinstalling Logseq by overwriting with 0.9.10, but did not work Thought it might be disk permissions, but didn't see it listed for full disk access

Reproduce the Bug

1. Installed Sonoma 17
2. Ran Logseq
3. Logseq locks up with spinning beach ball. Cannot do anything in the app

Expected Behavior

The app would run and allow edits

Screenshots

No response

Desktop or Mobile Platform Information

Mac Studio M1 Max macOS Sonoma Version 14.0 Beta (23A5286) Logseq Desktop version 0.9.10

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• [ ] I'm willing to submit a PR (Thank you!)

[Bad3r]

Try to re-install logseq. Have you tested other electron apps such as vscode?

[clickbrain]

I mentioned in my issue, that I tried reinstalling with the newest version and overwrote the one on mac and no luck. Just tried vscode and it is working fine.

[clickbrain]

Tried deleting it and resinstalling it again and still no love. It locks up immediately after starting.

By the way. this is on an Apple Mac Studio with M1, so I am using the Arm64 version.

Interestingly, this time it just locks up without the beach ball. Doesn't crash, just can't do anything in the UI at all. No matter where I click, the application might as well be a screenshot.

[clickbrain]

Is there any chance that a plugin could be causing the issue?

If so, is there a way to edit a text file to disable them to see, since I can't use the plugins interface?

[clickbrain]

Sorry for all the message. II went to quit it again. Right clicked on the icon on the task bar and when I clicked Quit, some of the random text I had typed earlier trying to get the app to respond appeared on the screen. I can't do anything else, but thought it was strange that something actually happened. Still locked up though.

RIght click to Quit does not actually quit the app and I don't have Force Quit as an option. I have to change focus of the app and go to Apple menu to get to Force Quit.

macOS does not see it as needing a Force Quit though in the list. It is there, but normal.

UPDATE; After last force quit, I decided to restart one more time and now the app is working! Go figure. No idea why the 6th restart and second reinstall would actually work. I'll update here if it locks up again.

[Bad3r]

@clickbrain, thanks for the update. I'll try to update my test machine over the weekend to see if I can reproduce the issue.

[brnorman]

This happened to me today - I have vault on icloud and after a few minutes it synced up and started working

[John-Lin]

Same here. logseq shows spinning beach ball and stuck when I upgrade to Sonoma.

[kcergfalo]

This happened to me today - I have vault on icloud and after a few minutes it synced up and started working

Same here: after a few minutes of beach balling it started working

[faze2ezaf]

Same issue happened to me. I think it might be a iCloud access issue. After downloading the whole Logseq folder on iCloud to computer it works fine now.

[yangze68]

Same issue happened to me. I think it might be a iCloud access issue. After downloading the whole Logseq folder on iCloud to computer it works fine now.

thanks, it works

[rasijr]

Hello,

Same problem here with OS Sonora. With logseq files in icloud or onedrive always the same problem: at some point logseq crashes and does not respond. Is there any solution or platform to leave files in the cloud that does not cause this problem?

Thanks!

[Eqxlt]

Hello,

Same problem here with OS Sonora. With logseq files in icloud or onedrive always the same problem: at some point logseq crashes and does not respond. Is there any solution or platform to leave files in the cloud that does not cause this problem?

Thanks!

Has this issue ever been address? My LogSeq is unusable at this point. I have even reverted to earlier versions, but still beach ball.

[github-actions[bot]]

Hi There! 👋

We haven't seen any activity on this issue in a while :sleeping:, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉 We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

• Forum: https://discuss.logseq.com
• Blog: https://blog.logseq.com
• Docs: https://docs.logseq.com

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!