Nextcloud desktop client keeps crashing in an infinite loop

[janstalhut]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I have searched for it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Since the update from version 34.0.0 to 34.0.1, the Nextcloud desktop client has been crashing repeatedly in an endless loop. The Nextcloud icon briefly appears in the GNOME system tray—as if about to start syncing—and then immediately disappears. After about 5 seconds, it reappears, and the cycle repeats endlessly.

Additionally, this issue causes the focus to shift away from the currently active application whenever the app restarts, making it impossible to work effectively on the computer.

Steps to reproduce

1. update via apt to Version 34.0.1
   ...

Expected behavior

The client should run continuously in the background after startup.

Which files are affected by this bug

no files affected

Operating system

Linux

Which version of the operating system you are running.

Ubuntu 24.04

Installation method

Community PPA (please test with the AppImage package ?)

Nextcloud Server version

34.0.2

Nextcloud Desktop Client version

34.0.1

Did this occur after an update or on a clean installation?

Minor version update (i.e. 33.0.0 → 33.0.1)

Are you using the Nextcloud Server Encryption module?

No

Are you using an external user-backend?

• Default internal user-backend
• LDAP or Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

Additional info

The endlessly repeating entries in the syslog:

2026-08-05T15:59:17.476214+02:00 Jans-PC-Bassum systemd[6117]: com.nextcloud.desktopclient.nextcloud.service: Scheduled restart job, restart counter is at 74. 2026-08-05T15:59:17.503175+02:00 Jans-PC-Bassum systemd[6117]: Started com.nextcloud.desktopclient.nextcloud.service - Nextcloud desktop user service. 2026-08-05T15:59:17.777541+02:00 Jans-PC-Bassum gnome-shell[6956]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4400008 specified for 0x4400006. 2026-08-05T15:59:18.057102+02:00 Jans-PC-Bassum tracker-miner-fs-3[21917]: (tracker-extract-3:21917): GLib-GIO-WARNING **: 15:59:18.056: Error creating IO channel for /proc/self/mountinfo: Das Argument ist ungültig (g-io-error-quark, 13) 2026-08-05T15:59:18.081267+02:00 Jans-PC-Bassum gnome-keyring-d[6151]: asked to register item /org/freedesktop/secrets/collection/login/545, but it's already registered 2026-08-05T15:59:18.291728+02:00 Jans-PC-Bassum gnome-keyring-d[6151]: asked to register item /org/freedesktop/secrets/collection/login/564, but it's already registered 2026-08-05T15:59:18.797411+02:00 Jans-PC-Bassum kernel: __vm_enough_memory: pid: 21903, comm: Thread (pooled), bytes: 24352464572416 not enough memory for the allocation 2026-08-05T15:59:18.797439+02:00 Jans-PC-Bassum kernel: __vm_enough_memory: pid: 21903, comm: Thread (pooled), bytes: 24352464572416 not enough memory for the allocation 2026-08-05T15:59:18.797448+02:00 Jans-PC-Bassum kernel: __vm_enough_memory: pid: 21903, comm: Thread (pooled), bytes: 24352464568320 not enough memory for the allocation 2026-08-05T15:59:18.797450+02:00 Jans-PC-Bassum kernel: __vm_enough_memory: pid: 21903, comm: Thread (pooled), bytes: 24352464703488 not enough memory for the allocation 2026-08-05T15:59:18.797717+02:00 Jans-PC-Bassum nextcloud[21894]: terminate called after throwing an instance of 'std::bad_alloc' 2026-08-05T15:59:18.797769+02:00 Jans-PC-Bassum nextcloud[21894]: what(): std::bad_alloc 2026-08-05T15:59:19.892649+02:00 Jans-PC-Bassum systemd[6117]: com.nextcloud.desktopclient.nextcloud.service: Main process exited, code=dumped, status=6/ABRT 2026-08-05T15:59:19.892935+02:00 Jans-PC-Bassum systemd[6117]: com.nextcloud.desktopclient.nextcloud.service: Failed with result 'core-dump'. 2026-08-05T15:59:24.975951+02:00 Jans-PC-Bassum systemd[6117]: com.nextcloud.desktopclient.nextcloud.service: Scheduled restart job, restart counter is at 75. 2026-08-05T15:59:24.993949+02:00 Jans-PC-Bassum systemd[6117]: Started com.nextcloud.desktopclient.nextcloud.service - Nextcloud desktop user service. 2026-08-05T15:59:25.257243+02:00 Jans-PC-Bassum gnome-shell[6956]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4400008 specified for 0x4400006. 2026-08-05T15:59:25.567373+02:00 Jans-PC-Bassum gnome-keyring-d[6151]: asked to register item /org/freedesktop/secrets/collection/login/545, but it's already registered 2026-08-05T15:59:25.758153+02:00 Jans-PC-Bassum gnome-keyring-d[6151]: asked to register item /org/freedesktop/secrets/collection/login/564, but it's already registered 2026-08-05T15:59:25.802084+02:00 Jans-PC-Bassum gnome-keyring-d[6151]: asked to register item /org/freedesktop/secrets/collection/login/564, but it's already registered 2026-08-05T15:59:26.254131+02:00 Jans-PC-Bassum nextcloud[22007]: terminate called after throwing an instance of 'std::bad_alloc' 2026-08-05T15:59:26.254189+02:00 Jans-PC-Bassum nextcloud[22007]: what(): std::bad_alloc 2026-08-05T15:59:27.353370+02:00 Jans-PC-Bassum systemd[6117]: com.nextcloud.desktopclient.nextcloud.service: Main process exited, code=dumped, status=6/ABRT 2026-08-05T15:59:27.353492+02:00 Jans-PC-Bassum systemd[6117]: com.nextcloud.desktopclient.nextcloud.service: Failed with result 'core-dump'.

[janstalhut]

Workaround: Uninstall nextcloud-desktop via apt, download and start AppImage version.

[uusijani]

Not sure if relevant, but starting from commandline also mentions Qt and Wayland:

qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

(qtwayland5 is installed on my system)

[janstalhut]

a start from commandline on my device shows only:

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Abgebrochen (Speicherabzug geschrieben)

I'm also using a standard ubuntu desktop environment with wayland

[RayCulp]

I'm seeing the same behavior on Linux Mint 22.3 Cinnamon using X11.
Error message when started from terminal:

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

[UnderEu]

Same issue on LMDE 7 (Linux Mint Debian Edition) - Packages from this PPA (jammy release).

Downgraded to 34.0.0 for now

[kevin-koellmann]

Same problem for me (on Linux Mint 22.3 Cinnamon using X11).

Workaround with AppImage doesn't work for me as well, when starting via GUI nothing happens. Starting via CLI results in:

AppImage CLI start log

kevin@INV1900173:~/Applications$ ./Nextcloud-34.0.1-x86_64_e0170eb6b32cbbf155c0a1e29c71c346.AppImage
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_shall_not_be_integrated : sqfs_open_image error: /home/kevin/Applications/Nextcloud-34.0.1-x86_64_e0170eb6b32cbbf155c0a1e29c71c346.AppImage
AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1)
Squashfs image uses (null) compression, this version supports only xz, zlib.
ERROR: appimage_is_terminal_app : sqfs_open_image error: /home/kevin/Applications/Nextcloud-34.0.1-x86_64_e0170eb6b32cbbf155c0a1e29c71c346.AppImage
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
Can't open squashfs image: Bad address

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
execv error: No such file or directory

EDIT: The AppImage problem seems to come from appimagelauncher. I'll try without.

EDIT2: Yes, as suspected, without appimagelauncher the AppImage is working 👍

EDIT3: Added OS info.

[oxivanisher]

This also happens on the "normal" Linux Mint Desktop.

[camilasan]

Downgraded to 34.0.0 for now

so this is really only happening with 34.0.1?