Description
- 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 installing the client through the official Fedora RPM Repository, setting showExperimentalOptions=true
under [General]
in the config file under ~/.config/Nextcloud/nextcloud.cfg
and signing in to my Nextcloud instance, the option for virtual file support won't show up. This is only the case on my Fedora instance, using Ubuntu 24.04 everything just worked fine. If you decide to turn on virtual file support later by going to the settings of the client and some of your synchronizations, the client crashes when clicking Enable virtual file support (experimental)
.
Steps to reproduce
- Install Nextcloud client through the official Fedora RPM repo
- Enable experimental options in the config file
- Start client and log in to your instance
- No virtual file support shows up
- Setup any sync rule
- Go into settings
- Click the three dots on the side of the sync rule
- Click
Enable virtual file support (experimental)
Expected behavior
Virtual file support should be available after the first login and the client shouldn't crash when activating the support for it later.
Which files are affected by this bug
nextcloud.cfg
Operating system
Linux
Which version of the operating system you are running.
Fedora 40 Workstation, Kernel 6.8.11-300
Package
Distro package manager
Nextcloud Server version
29.0.2
Nextcloud Desktop Client version
3.13.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 Enabled
Are you using an external user-backend?
- Default internal user-backend
- LDAP/ Active Directory
- SSO - SAML
- Other
Nextcloud Server logs
No response