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
In version 3.13.1-1 of the Nextcloud client, virtual file support being enabled prevents the client from launching. When launching from the terminal, the /usr/bin/nextcloud binary crashes with Aborted (core dumped). The return code appears to be 134 from echo $?.
Downgrading to 3.13.0 with a cached package and changing no other packages or configuration allows the application to launch and function normally, with virtual file support being operational.
I have not tested in non-Arch distributions, but this version does operate as expected in a Windows VM. I have tested on two separate Arch installs, one AMD CPU- and GPU-based, the other Intel + Nvidia. Both crash.
The Arch 3.13.1 package is built from the initial release of that version. The Nextcloud project silently dropped the release and retagged something like 3 days later with no explanation. (Don't do that @nextcloud, if something is wrong with your release or release process tag a new version and move on and save users and packagers a lot of headaches!)
Just to chime in here for anyone else having this issue.
I just recently updated my distro and had this exact issue with this exact version.
I ran this to see what versions were available to me. Luckily, 3.11.0-1.1 was listed.
apt-cache show nextcloud-desktop | grep Version
I installed that version with the below command and my virtual files worked again! I also made sure to put it on hold so it doesn't automatically update on me and break again until they have it sorted.
Bug description
In version
3.13.1-1
of the Nextcloud client, virtual file support being enabled prevents the client from launching. When launching from the terminal, the/usr/bin/nextcloud
binary crashes withAborted (core dumped)
. The return code appears to be134
fromecho $?
.Downgrading to
3.13.0
with a cached package and changing no other packages or configuration allows the application to launch and function normally, with virtual file support being operational.I have not tested in non-Arch distributions, but this version does operate as expected in a Windows VM. I have tested on two separate Arch installs, one AMD CPU- and GPU-based, the other Intel + Nvidia. Both crash.
Independently confirmed by @christian-heusel, who also provided the following crash backtrace (https://gitlab.archlinux.org/archlinux/packaging/packages/nextcloud-client/-/issues/6).
Steps to reproduce
nextcloud-client
viapacman
to3.13.1-1
Expected behavior
Program should not exit quickly with an error code.
Which files are affected by this bug
N/A
Operating system
Linux
Which version of the operating system you are running.
Arch Linux
Package
Distro package manager
Nextcloud Server version
29.0.3 and 29.0.2
Nextcloud Desktop Client version
3.13.1
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
Reported to Arch here: https://gitlab.archlinux.org/archlinux/packaging/packages/nextcloud-client/-/issues/6
The text was updated successfully, but these errors were encountered: