Cannot launch Nextcloud linux appimage since update 4.0.5

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).

Hello.

Today, I updated my Nextcloud linux desktop client appimage to 4.0.5. The new version cannot start. When trying to launch the client in a linux terminal, I get the following error :

./Nextcloud-4.0.5-x86_64.AppImage: symbol lookup error: /tmp/.mount_NextclPHpGcK/usr/bin/../lib/libgobject-2.0.so.0: undefined symbol: g_string_copy

The previous version 4.0.4 still starts without issue.

I am using linux mint debian edition 7. All updates have been applied.

Thanks for your help.

Christophe

1 Like

Exactly same problem hier on LMDE6 Faye.

Same problem here

1 Like

Some problem with my notebook here, i’m using Ubuntu 24.04.3 LTS default desktop environment. Please help fix this issue.

1 Like

Same as a Test with Xubuntu 25:10

adelaar@xubuntu25-10:~$ bin/Nextcloud-4.0.5-x86_64.AppImage 
bin/Nextcloud-4.0.5-x86_64.AppImage: symbol lookup error: /tmp/.mount_NextclgbLMdf/usr/bin/../lib/libharfbuzz-subset.so.0: undefined symbol: hb_free
adelaar@xubuntu25-10:~$ 

Same with Debian 13.2

Unfortunately, I don’t have a solution for the AppImage issue, since I’m using Arch, btw :wink: and therfore always get the latest client in a timely manner from the official repositories, and I already received version 4.0.5, which is working fine.

For those of you using (X)ubuntu, you might want to use the PPA instead of the AppImage, so the client is updated automatically to the latest version via the regular system updates. That’s what I used back when I was still on Ubuntu: Desktop client : “Nextcloud development” team

By the way, there are already three bug reports on GitHub, all right next to each other, so it definitely seems to be a widespread issue, both the actual problem itself and the fact that people apparently don’t even look at the existing issues at the top of the list before opening a new one. :roll_eyes:

I’d say the best options for now are to roll back to the previous version and wait until the issue is fixed, or switch to the PPA or another source.

We are aware of the issue and we are looking for a solution. Check the GH issues for an update.

3 Likes

Same issue with Nextcloud 4.0.6 Ubuntu 24.04.3 LTS/Gnome. The process is launched but the synchronization is not working and the icon is not displayed. Back to Nextcloud 4.0.4.

Glad to tell you that 4.0.6 is working again on LMDE6 Faye.

Just updated from 4.0.4 to 4.0.6 on Linux Mint 23.3. The AppImage still crashes, but with a new error message:
Failed to initialize instances shared memory: “QSharedMemory::handle: doesn’t exist”
XIO: fatal IO error 17 (Die Datei existiert bereits) on X server “:0”
after 470 requests (470 known processed) with 0 events remaining.

I can confirm the same error. With the first App-Image Instance it shows “The X11 connection broke: No error (code 0)” the second round one runs the App-Image it shows exactly what you reported with “XIO: fatal IO error 17 (Die Datei existiert bereits) on X server “:0”
after 459 requests (459 known processed) with 0 events remaining”.
Clearing the config folder in that sense that I renamed it to backup just to check if that was it, doesn’t help here either.
Would love to get it going again, if someone can point in the right direction here?

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.