AppImage uses libfuse2, but newer distros use libfuse3

[mikerspencer]

Search first

• I searched and no similar issues were found

What Happened?

I downloaded the logseq appimage (0.9.18), made it executable and tried to run it on Ubuntu 23.04. The app would not launch because libfuse.so.2 was not installed.

I believe libfuse3 has largely superseded v2 and running both leads to issues with Gnome. Hence it is not currently possible to run Logseq on newer versions of Ubuntu.

Reproduce the Bug

1. try and run logseq appimage from the file system on Ubuntu 23.04
2. try again from a terminal and view the bug

Expected Behavior

Logseq runs

Screenshots

No response

Desktop or Mobile Platform Information

Ubuntu 23.04 with Logseq 0.9.18

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!)

[sprocketc]

@mikerspencer Hello! That seems to be a problem for all AppImages on newer Ubuntu distros.

Fuse 2 is required by the appimage toolchain. Unfortunately (as you already stated), installing libfuse2 might not be a viable option as of 22.04, because it might introduce major issues. This is already flagged as "won't fix" on launchpad.

Until this is resolved, you could try this fallback method, or install Logseq using a third party package (e.g. through flathub or snapcraft)

[mikerspencer]

Thanks @sprocketc ! Extracting the appimage worked well.

[github-actions]

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, 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!