Is this a new report?
Yes
System Info
Void 7.2.2_1 x86_64 AuthenticAMD uptodate rFFF
Package(s) Affected
nextcloud-client-34.0.4_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
Not that I could find.
Expected behaviour
The VFS plugins should either:
Be installed directly into the directory expected by the Nextcloud client:
/usr/lib/qt6/plugins/
Or, alternatively, the package/build configuration should explicitly configure the client to search the directory where the distribution installs the plugins.
The installation path should be consistent with the path used by the upstream build/client at runtime.
Actual behaviour
The plugins are installed in:
while the client only searches:
Consequently, VFS support is unavailable on a clean installation until the user manually creates symlinks.
Steps to reproduce
Install the nextcloud-client package on a Qt6-based system.
Verify that the VFS plugins are installed:
xbps-query -f nextcloud-client | grep -E 'vfs|nextcloudsync|/usr/lib'
The output shows:
/usr/lib/nextcloudsync_vfs_suffix.so
/usr/lib/nextcloudsync_vfs_xattr.so
Start the Nextcloud client:
Trace the filesystem lookups performed by the client:
strace -f -e trace=openat,access,stat,statx nextcloud 2>&1 | grep -E 'nextcloudsync|vfs_'
Observe that the client searches for the VFS plugins in /usr/lib/qt6/plugins/:
statx(..., "/usr/lib/qt6/plugins/nextcloudsync_vfs_suffix.so", ...) = -1 ENOENT
statx(..., "/usr/lib/qt6/plugins/nextcloudsync_vfs_xattr.so", ...) = -1 ENOENT
Verify that the files actually exist, but in a different directory:
ls -l /usr/lib/nextcloudsync_vfs_*.so
Create symlinks to the location searched by the client:
sudo ln -s /usr/lib/nextcloudsync_vfs_suffix.so \
/usr/lib/qt6/plugins/nextcloudsync_vfs_suffix.so
sudo ln -s /usr/lib/nextcloudsync_vfs_xattr.so \
/usr/lib/qt6/plugins/nextcloudsync_vfs_xattr.so
Restart the Nextcloud client.
Observe that the VFS plugins are now detected and virtual files become available.
Is this a new report?
Yes
System Info
Void 7.2.2_1 x86_64 AuthenticAMD uptodate rFFF
Package(s) Affected
nextcloud-client-34.0.4_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
Not that I could find.
Expected behaviour
The VFS plugins should either:
The installation path should be consistent with the path used by the upstream build/client at runtime.
Actual behaviour
The plugins are installed in:
while the client only searches:
Consequently, VFS support is unavailable on a clean installation until the user manually creates symlinks.
Steps to reproduce
Install the nextcloud-client package on a Qt6-based system.
Verify that the VFS plugins are installed:
The output shows:
Start the Nextcloud client:
Trace the filesystem lookups performed by the client:
Observe that the client searches for the VFS plugins in /usr/lib/qt6/plugins/:
Verify that the files actually exist, but in a different directory:
Create symlinks to the location searched by the client:
Restart the Nextcloud client.
Observe that the VFS plugins are now detected and virtual files become available.