It is quite frustrating to realize that I want access to a file that should have been synced on my home system, but is NOT synced because this application stopped running—and I have no way to restart the appimage on my home machine while I’m at work. This is absolutely maddening behavior. When the application was just a regular installed program, it NEVER stopped running. It worked predictably and reliably. The appimage has been AWFUL and has never worked correctly.
The ability to sync files to a central cloud location is the main reason I use Nextcloud, so this appimage issue defeats the entire purpose (for me, anyway).
Also, is there a better place to ask this question & find support for this issue?
Nextcloud version:
Nextcloud-3.6.4-x86_64.AppImage
Operating system and version:
Kubuntu 22.10
Kernel version: 5.19.0-28-generic (64-bit)
KDE Frameworks Version: 5.98.0
Qt Version 5.15.6
Graphics Platform: X11
The issue you are facing:
The app image doesn’t stay running in the background and sync changes as they happen. It starts running when the system boots up, syncs changes, then SILENTLY quits and never restarts. If I want to sync changes (after I figure out it stopped running), I must manually restart the app image.
Expected behavior:
Once the system boots up, the appimage syncs and KEEPS RUNNING to sync changes in the background. (The way the regular, installed Nextcloud app worked on my very old version of Fedora.)
How do I make this happen?
Is this the first time you’ve seen this error?:
No. This has been happening since Nextcloud appimage version 3.6.0 (when I started using the appimage).
Steps to replicate it:
- Start appimage.
- Wait.
- Appimage stops running & never restarts.