You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Expected behaviour
Client should automatically update to newer version when one is available. When there is a new update, it should offers us to click once and auto-update as explain in Appimage doc (https://docs.appimage.org/packaging-guide/optional/updates.html#making-appimages-self-updateable). We should not need to download the appimage, replace the old by the new appimage file and then have to set a new launch on startup (as it is considered by the system as new app instead of an update of app). After successful update, he might say “the update was installed” and done....
Actual behaviour
Tell us what happens instead
We are invited to download the new appimage of the new version. Wee should do the job to remove the old appimage file from our system and set the new appimage file to launch on startup... It's a lot of work for simply updating.
Steps to reproduce
Client configuration
Client version: 3.0.3
Operating system:
OS language: Debian buster 10
Qt version used by client package (Linux only, see also Settings dialog): 5.11.3
Client package (From Nextcloud or distro) (Linux only): Appimage
Installation path of client: /home/xxxx/applications/
The text was updated successfully, but these errors were encountered:
How to use GitHub
Expected behaviour
Client should automatically update to newer version when one is available. When there is a new update, it should offers us to click once and auto-update as explain in Appimage doc (https://docs.appimage.org/packaging-guide/optional/updates.html#making-appimages-self-updateable). We should not need to download the appimage, replace the old by the new appimage file and then have to set a new launch on startup (as it is considered by the system as new app instead of an update of app). After successful update, he might say “the update was installed” and done....
Actual behaviour
Tell us what happens instead
We are invited to download the new appimage of the new version. Wee should do the job to remove the old appimage file from our system and set the new appimage file to launch on startup... It's a lot of work for simply updating.
Steps to reproduce
Client configuration
Client version: 3.0.3
Operating system:
OS language: Debian buster 10
Qt version used by client package (Linux only, see also Settings dialog): 5.11.3
Client package (From Nextcloud or distro) (Linux only): Appimage
Installation path of client: /home/xxxx/applications/
The text was updated successfully, but these errors were encountered: