Update to 3.16.5 (ZorinOS 17) causes Desktop-Client to crash due to filesystem errors

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x): 31.0.6.2
  • Operating system and version (e.g., Ubuntu 24.04): ZorinOS 17.3 Pro
  • Web server and version (e.g, Apache 2.4.25): NGinx
  • Reverse proxy and version _(e.g. nginx 1.27.2) NGinx
  • PHP version (e.g, 8.3): 8.3
  • Is this the first time you’ve seen this error? (Yes / No): Yes
  • When did this problem seem to first start? Update to client 3.16.5
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.) native ZorinOS packages
  • Are you using CloudfIare, mod_security, or similar? (Yes / No) No

Summary of the issue you are facing:

nextcloud.gui.application: Failed to move the old config directory to its new location ( "/home/%USER/.local/share/Nextcloud" to "/home/%USER/.config/Nextcloud" )

  what():  filesystem error: Cannot convert character sequence: Ungültiges oder unvollständiges Multi-Byte- oder Wide-Zeichen

terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_e

Steps to replicate it (hint: details matter!):

  1. update via App-Store and / or apt update && apt full-upgrade the Desktop-Client
  2. Version <3.16.5 to 3.16.5
  3. NC-Client Start and terminates after seconds
  4. Stop all Synchronisation (pause)
  5. restart NC-Client → see that NC-Desktop-Client remains open => not closing
  6. continue Synchronisation
  7. see that NC-Desktop Client crash in between seconds

Log entries

see above → error messages come from the log not from the gui / desktop

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

nothing on the server side!

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

vivaldi (chromium) 7.4.3684.50 (Stable channel) stable (64-Bit)

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

nothing to see on the server side

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

...

Additional Infos

I am using the client that way
not synching the whole cloud but selected folders e.g. Documents, Pictures, etc. etc.
So i have several sync jobs instead of “one for all”

Not tested if it makes any difference if i switch … but that means uninstall → re-install, correct?

Update:
investigated that if starting nextcloud-desktop and very, very quickly click on taskbar /tray to stop all synching client remains open.
After that re-initiate synching folder for folder …
With Documents, Pictures, Musik, Video and Shares only one of them is sufficient to crash client.
Downloads, and some very small folders could be synched without crashing the desktop client.
Now the further question - how to investigate which element / file(s) / folder(s) are affected??

In ZorinOS all of the “standard” folders Documents, Pictures, Musik and Video are also set in nautilus to point to the ../ Nextcloud / so i can open all of them from nautilus filemanager directly. Was not a problem until this latest version 3.16.5 …

:thinking:

Had the same problem here with Mint 21.3:

  • Selfhosted Server with every package auto-upgraded
  • Client 3.16.5

After Nextcloud Client has been upgraded (System Package, 3.16.5-20250613.191603.930e6e637-1.0~jammy1), same symptoms like the ones described above. No error log: The client just exits.

I have some other clients here (Windows, Mac OS), which are working perfectly with the 3.16.5 version.

Solved it (temporarily) by uninstalling the system package and using the 3.16.4 AppImage Bundle from Index of /desktop/releases/Linux.

1 Like

Many thanks for your reply.

Interestingly also the Nextcloud-3.16.5-x86_64.AppImage did what i would expect from the desktop client.
Nice, that the AppImage uses the path /home/$USER/.config/Nextcloud for searching the nextcloud.cfg so all configured till now is allready in!

Also nice, the autostarter in ZorinOS works like the native app
/path/to/Nextcloud-3.16.5-x86_64.AppImage --background %u
works out of the box. So the client starts minimized in tray.

That is also irritating …

Failed to move the old config directory to its new location ( “/home/%USER/.local/share/Nextcloud” to “/home/%USER/.config/Nextcloud” )

This path /home/%USER/.local/share exist but without any config.
Just the logfiles for the synch folders reside in there …
:thinking:

So for now i give the workaround way to start at system startup and hope future native desktop versions could solve this problem …