Virtual File Support Crashes Application in 3.13.1-1 with Code 134

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 with Aborted (core dumped). The return code appears to be 134 from echo $?.

Downgrading to 3.13.0 via downgrade with a cached package and changing no other packages allows the application to launch and function normally, with virtual file support being operational.

I have not tested in non-Arch distributions, so this could be an upstream bug. I have tested on two separate Arch installs, one AMD CPU- and GPU-based, the other Intel + Nvidia. It appears to operate as expected on Windows with the same version following a bug report and from testing in a VM.

Additional info:

• package version(s): 3.13.1-1 with the server running Nextcloud Hub 8 (29.0.2)
• config and/or log files: Nothing relevant spotted in nc_sync.log. Enable experimental options in ~/.config/Nextcloud/nextcloud.cfg under [General] with showExperimentalOptions=true and have virtual file support enabled on a folder sync connection
• link to upstream bug report, if any: No identical ones currently found. Closest one is https://github.com/nextcloud/desktop/issues/6877 but it appears that the application still launches on a Windows system.

Steps to reproduce:

Tested on multiple Arch systems, all with Gnome.

1. Enable experimental options and have virtual file support enabled on a folder sync connection
2. Update nextcloud-client via pacman to 3.13.1-1
3. Client will no longer launch
4. Downgrading the package without changing config files will allow it to operate again as expected