-
Notifications
You must be signed in to change notification settings - Fork 29
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
AppImage fallback when libfuse is not present is not working in Ubuntu LXC container #251
Comments
Initial issue nextcloud/richdocuments#3190 |
Hi @samvde - I just realized you're running the AppImage directly? That's not how Lines 89 to 90 in b7fe65d
In this case, things are operating as expected, given that you're doing things in an unconventional way. :) |
Perhaps I was not explicit enough in my initial report. I start it manually (or now via systemd) because it does not get autostarted ever. Loading a document gives and eternal spinner. So it is not by choice. I have seen a lot of bug reports about people getting eternal spinners especially on snap installations, it took a while to get it figured out. Perhaps it is a safe workaround to make it default for that use case, not sure. |
I think this issue might be caused because Ubuntu made fuse3 the default. E.g. AppImage/AppImageKit#1194 Not sure you can add libfuse2 to the snap or something like that but I think it breaks for everyone using the Nextcloud snap out of the box on at least Ubuntu and/or Debian-based distributions. |
The documentation of this project states that libfuse is optional, but this is not my experience:
I use NextCloud, installed as a snap in an Ubuntu LXC container, and discovered I have to run the Collabore AppImage manually to get online editing functionalities. Without it, I get the "loading" spinner forever when opening a document.
I added a systemd unit to start it after boot, but did a re-test to make sure this was my issue:
Start: Online editing working.
Online editing not possible.
Online editing not possible.
Online editing works again.
The text was updated successfully, but these errors were encountered: