Bug 2362431

Summary: Not able to activate vfs due to missing plugin
Product: [Fedora] Fedora Reporter: mathisloge
Component: nextcloud-clientAssignee: Mukundan Ragavan <nonamedotc>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 42CC: gwync, jan.public, louisxavier.lefranc, martin.abbrent+fedoraproject.org, michel, nb, nonamedotc, redhat, uwe.arnold
Target Milestone: ---Keywords: Desktop
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://github.com/nextcloud/desktop/issues/6819#issuecomment-2831962584
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch proposal none

Description mathisloge 2025-04-26 08:50:41 UTC 
When enabling the virtual filesystem support in the nextcloud client, it tries to load the plugin `nextcloudsync_vfs_suffix` however somehow it can't be even found.
It would have been built in here https://github.com/nextcloud/desktop/blob/48f65841520bde6b84d13edab3dfb33458e5a59e/src/libsync/vfs/CMakeLists.txt

 
When I'm building it from source, it won't crash. Therefore I guess its some packaging problem

Reproducible: Always

Steps to Reproduce:
1. enable the virtual filesystem
2. it crashes when saving the settings


Expected Results:
The client does not crash and can load the virtual filesystem plugin

See https://github.com/nextcloud/desktop/issues/6819#issuecomment-2831962584
Comment 1 louisxavier.lefranc 2025-09-24 01:26:35 UTC 
Created attachment 2107438 [details]
Patch proposal

Hi,

A compiler option to define the correct destination path for vfs plugins was missing. I added it and it doesn't seem to crash anymore.

I was also wondering about the relevance of putting these plugins in the devel package rather than libs. What's your opinion on this ?
Comment 2 mathisloge 2025-10-01 14:46:00 UTC 
Hi,

from a user’s perspective, I would prefer to have it included directly in the nextcloud-client package. Since it is required for the client’s VFS functionality, it would feel odd to need to install the development package just to enable standard GUI functionality.
Comment 3 louisxavier.lefranc 2025-10-12 09:51:26 UTC 
I agree with you, I've been using this feature for years without any issues. However, Nextcloud continues to consider this feature experimental since you still need to enable "showExperimentalOptions".
It's up to the maintainers to decide. I hope they'll at least implement the patch I proposed soon.