-
Notifications
You must be signed in to change notification settings - Fork 817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Unable to activate virtual files on setup and after setting up a synchronization using rpm client #6819
Comments
Same issue on Fedora 40 and client version 3.13.0. |
I'm curious, has it ever worked in Fedora? When I distro-hopped a few years ago, this was one of the things that prevented me from using it. It seems part of the issue for Arch (check the related issue above) recently was the build process was not including various directories, including plugins. Maybe this is a similar downstream issue? |
You're right, I don't remember this every working on fedora. That and the nextcloud-plugin-dolphin package to see which files were stored locally. I've been using fedora for years, but now starting to use nextcloud in a business environment. |
Does the same thing occur if you use our AppImage? Also, can you try running the client from a command-line window to see what the crash output indicates? The log appears to be empty from what I presume is the crash time period. Also, try with a more up-to-date RPM (3.13.2) since it wasn't built against qt6 until then from the looks of it: e.g. see #6577 & https://bugzilla.redhat.com/show_bug.cgi?id=2299950 |
RPM Test
Console:
I couldn't activate VFS because the UI doesn't show any options to configure existing accounts or add a new account: AppImage test coming up EDIT I've downloaded nextcloud client and dolphin package and will retry with those EDIT 2: Installed from https://koji.fedoraproject.org/koji/taskinfo?taskID=122098706
Someone in there (https://bugzilla.redhat.com/show_bug.cgi?id=2299950) says it works, and maybe it does, but I still don't see the UI elements to add account. I have this bug on both Fedora KDE latest and Fedora Kinoite Latest. Enabling VFS throws in console:
There is so many log files and so many logs in each of them, I didn't see anything relevant yet and I didn't clear up the logs before testing :/ I'll retry later today or tomorrow to try and get a log file about that. |
same problem here with nobara (fedora based) and KDE 6 |
In openSUSE TW, I set showExperimentalOptions=true in the nextcloud config file but no options for virtual file system is present, so, this setting doesn't do anything. |
For me it worked on Fedora (even with experimental virtual files) until version 3.13.2. I have also the following error during synchronisation running with version 3.13.3.
And for versions 3.14.XXX and above, I am not even able to open the app and I have this issue #7465 |
are any of you using or accessing read only folders? |
Yes, there are read-only folders. |
We have not been able to reproduce this yet :/ |
are you using virtual files on linux (experimental feature)? |
@loulous24 are you also using virtual files on linux (experimental feature)? |
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 clickingEnable virtual file support (experimental)
.Steps to reproduce
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?
Nextcloud Server logs
No response
Additional info
Client logs after crash
The text was updated successfully, but these errors were encountered: