I switched to Nextcloud AIO on my server later in 2024. However, I had hoped that my Linux desktop client on Ubuntu would perform faster.
Let me explain:
When I right-click the Nextcloud icon in the taskbar, it can take up to 3 minutes for the menu to appear. Sometimes, I even have to kill the client and restart it just to change sync options.
Is this normal behavior? Is the Linux client really this slow?
What you’re describing is definitely not typical behavior for the Nextcloud client on Linux. The menu should appear almost instantly or within just a few seconds at most. Here are a few tips that might help:
Try a newer version or a different installation method
The current version 3.16.0 is available as an AppImage, which you can download from GitHub. If you’ve been using Snap or Flatpak, the sandboxing might be causing slowdowns. Sometimes switching to a .deb package or using the AppImage can resolve performance issues.
Monitor system load and check logs
While you’re waiting for the menu to appear, open top or htop to see if the Nextcloud client or other processes are consuming a lot of CPU or RAM.
You can also run the client via nextcloud --logdebug to view any error messages or warnings. These can help pinpoint where the issue lies.
Check the scope of your synchronization
Syncing large numbers of files or folders can temporarily overload the client and slow down its responsiveness. Try temporarily disabling the sync for less critical folders and see if that improves performance.
Verify server load and connection
While not the most common cause, you should check if your Nextcloud server is under heavy load or if your internet connection is too slow (e.g., if you’re syncing large files over a weak link). In cases of extreme server load, the client’s response time can suffer.
I hope one of these steps helps resolve the issue. If you notice any improvement—or if the problem persists—let us know so we can better identify the cause and suggest further steps.
I’m glad to hear the Flatpak version is performing better for you. Regarding the AppImage:
By default, it does not include an automatic updater. You’d typically need to manually download the latest AppImage whenever a new release comes out.
However, there is a tool called AppImageUpdate that can help manage updates for AppImages if the application supports it. You’d still have to run it yourself, but it saves you from having to manually fetch each new file.
If you prefer having updates handled automatically, it’s usually best to stick with a package format like Flatpak or a distribution-specific repository, which take care of updates through your package manager.
Personally, I use the version from the repositories myself. I’m on CachyOS, where updates become available almost instantly as soon as there’s a new release. This provides a good balance between having the latest features and minimizing the hassle of manual updates.
Hope that clarifies things! If you run into any other issues, feel free to let us know.