⚠️ 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've searched 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

After updating to Nextcloud client 3.14.0, the client crashes either when enabling Virtual Files support, or if an existing configuration contains already enabled virtual file folders(will crash on startup).

Shortly before the crash, I found this in the logs:
2024-09-23 17:01:41:058 [ warning qt.core.qobject.connect unknown:0 ]: QObject::connect(QDialog, OCC::AccountSettings): invalid nullptr parameter

nextcloud-debug.zip

Steps to reproduce

1. Click the ... in settings next to a sync folder
2. Click to Enable Virtual Files support
   Client will crash after this.

If an already existing Virtual Files folder is in the configuration, simply start the client, it will crash on start.

Expected behavior

When clicking Enable Virtual Files support, Virtual File mode should be enabled for the folder.

If an already existing virtual files folder existing in the configuration, Nextcloud client should start and sync as normal.

Which files are affected by this bug

Nextcloud Client

Operating system

Linux

Which version of the operating system you are running.

Garuda Linux 6.10.5 Kernel, KDE Plasma 6.1.5, Wayland

Package

Official Linux AppImage

Nextcloud Server version

29.0.7

Nextcloud Desktop Client version

3.14.0

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

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

Nextcloud Server logs

No response

Additional info

This might be the cause of other crash on start bugs