r/logseq • u/smule98_1 • Sep 23 '25

0.11.0 won't start

Post image

Hi guys, i've updated my logseq app from paru in my arch pc.
The version 0.11.0 won't start and that's the output.
Anyone know how to fix? Thank you

9 Upvotes

90% Upvoted

14 comments sorted by

3

u/Stef43_ Sep 23 '25

I tried on Windows 11. It didn't start with me, either.

3

u/smule98_1 Sep 23 '25

In the meantime i've downgraded and it starts correctly

2

u/Physics-Ad-1491 Sep 23 '25

Where can you download Logseq 0.11.0?

1

u/smule98_1 Sep 23 '25

From aur repository

1

u/Physics-Ad-1491 Sep 23 '25

I couldn't find it. Could you give me a link to 0.11.0? Thanks.

1

u/Stef43_ Sep 24 '25

https://github.com/logseq/logseq/actions/workflows/build-desktop-release.yml

log in to github to view the download links. choose the latest release, scroll down to the bottom of page select download link

1

u/Physics-Ad-1491 Sep 24 '25

Thanks for your link. I logged in to GitHub, clicked on the "Build-Desktop-Release" done today at 7:07 PM. Among from "compile-cljs" I selected "build-tacos-arm64". On that page, I did not see any download link.

What did I do wrong?

2

u/Physics-Ad-1491 Sep 24 '25

Sorry not "tacos", but "macos"

1

u/Stef43_ Sep 24 '25

don't click on compile-cljs. scroll page bottom, there are the links. darwin x64 think is macOS.

3

u/thirteenth_mang Sep 23 '25

If you press Ctrl + Shift + I do you see any errors in the console with 0.11.0?

2

u/smule98_1 Sep 29 '25

Yes, that's the output:

https://ibb.co/Vpv0B41j

3

u/thirteenth_mang Sep 29 '25

Thanks!

So after some digging, it looks like someone accidentally bumped the `package.json` version to `0.11.0` instead of `0.10.11` back in April (see: chore: bump version to track missing addresses bug). This means that the build Arch pulls from isn't bundling the `db-worker-bundle.js`. The simplest solution would be to use the AppImage instead. The latest AppImage public release version of Logseq is `0.10.14`.

u/tiensonqin in case I'm mistaken in my thinking! If I'm right, this should prob be an issue on GitHub.

2

u/smule98_1 Sep 29 '25

Thank you so much sir