Ok starting with this message:
libsoup/http2/soup-client-message-io-http2.c · master · GNOME / libsoup · GitLab
libsoup/http2/soup-client-message-io-http2.c · master · GNOME / libsoup · GitLab
This error means, that the soup client cannot read the data from the server. Especially the body part…
It would useful to add debugging of http aswell.
pkill gvfs
pkill nautilus
export GVFS_DEBUG=1
export GVFS_HTTP_DEBUG=all # all or body or header
cd /usr/lib
./gvfsd-dav ssl=true user=username host=dav.example.org prefix=/remote.php/webdav/
Just outsource the log to another secure place (which you can delete), if you are scared to expose personal data.
For me it looks like that the iserv server use deprecated features, which has been removed on newer libs, but on Ubuntu it still works. But that is just a guess. Manjaro is rolling forward and if you need to work with such servers, then my best advice would be staying at a LTS release of Ubuntu / Debian and sort of, since iserv uses debian on their servers.
On my installation (unstable), I have 2 versions of libsoup:
$ ls -al /usr/lib/libsoup-[0-9].[0-9].so.[0-9].[0-9]*
-rwxr-xr-x 1 root root 653880 7. Jan 19:03 /usr/lib/libsoup-2.4.so.1.11.2
-rwxr-xr-x 1 root root 596488 1. Apr 00:28 /usr/lib/libsoup-3.0.so.0.0.5
It is a bit hacky, but you can try this…
Since gvfsd-dav is linked to libsoup-3.0.so.0, which is a symlink:
$ ldd gvfsd-dav | grep "soup"
libsoup-3.0.so.0 => /usr/lib/libsoup-3.0.so.0 (0x00007fcc46978000)
$ ls -al /usr/lib/libsoup-3.0.so.0
lrwxrwxrwx 1 root root 20 1. Apr 00:28 /usr/lib/libsoup-3.0.so.0 -> libsoup-3.0.so.0.0.5
we can symlink the old lib:
sudo ln -srfv /usr/lib/libsoup-2.4.so.1.11.2 /usr/lib/libsoup-3.0.so.0
Now gvfsd-dav should use v2.4 instead of v3.0.
Try to connect with DEBUG variables enabled.
Revert it:
sudo ln -srfv /usr/lib/libsoup-3.0.so.0.0.5 /usr/lib/libsoup-3.0.so.0
I searched the Ubuntu sources… Jammy (22.04) still uses libsoup2.4 :
libsoup2.4-1 (>= 2.58.2)
HTTP library implementation in C -- Shared library
Ubuntu – Details of package gvfs-backends in jammy
So that is the difference.