Bug 2093400

Summary: davs to nextcloud not working anymore with nautilus
Product: [Fedora] Fedora Reporter: Albert Flügel <af>
Component: libsoup3Assignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 37CC: caillon+fedoraproject, cosimo.cecchi, fschwarz, gnome-sig, gwync, mclasen, mcrha, oholy, philip.wyett, rhughes, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: libsoup3-3.2.2-3.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-06 01:54:31 UTC Type: Bug
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
Screenshot with the error message
none
output from coredump-ctl none

Description Albert Flügel 2022-06-03 15:44:11 UTC
Created attachment 1886433 [details]
Screenshot with the error message

Description of problem:
Cannot connect nautilus to nextcloud using davs anymore. It was working with Fedora 35.


Version-Release number of selected component (if applicable):
nautilus-42.1.1-1.fc36.x86_64

How reproducible:


Steps to Reproduce:
1. Open nautilus
2. Click + Other Locations on the left
3. Enter a valid webdavs address to a nextcloud instance in the entry field at tbe bottom starting with davs:// (https:// or webdavs:// is rejected)
4. In the popup window appearing enter your credentials

Actual results:
I get popup window with an error message:
Unable to access location
Remote peer disconnected
(please see the attached screenshot)

Expected results:
I see the contents of the remote directory in nautilus

Additional info:
It works with dolphin (who wants an address starting with "webdavs://", though). Before fedora 36 nautilus was working more reliably than dolphin, now dolphin is the choice.

Comment 1 Ondrej Holy 2022-06-06 05:53:39 UTC
Do you see this even with gvfs-1.50.2? If so, I will need a backtrace for gvfsd-dav to see what is going on...

Comment 2 Albert Flügel 2022-06-15 11:49:29 UTC
Yes, gvfs is gvfs-1.50.2-1.fc36 .
How to obtain the dump at the right time ? gvfsd-dav is not running permanently and i don't get a message, that a core is dumped.
A household recipe: don't break working things.

Comment 3 Felix Schwarz 2022-08-19 10:18:01 UTC
Created attachment 1906518 [details]
output from coredump-ctl

I think I'm experiencing the same problem so I'm uploading the output of coredumpctl. Do you need more information? I can also install/build RPMs with experimental patches if you need.

Comment 4 Felix Schwarz 2022-08-19 10:19:25 UTC
btw: I'm trying to a NextCloud instance. ping me if I should create a user so you can try/debug the problem directly.

Comment 5 Felix Schwarz 2022-08-19 10:30:37 UTC
I tried to gather additional debug data following https://wiki.gnome.org/Projects/gvfs/debugging#Getting_debug_logs

$ GVFS_DEBUG=1 $(find /usr/lib* -name gvfsd 2>/dev/null) --replace 2>&1 | tee gvfsd.log 
fuse: failed to access mountpoint /run/user/1004/gvfs: Transport endpoint is not connected
trash: Added new job source 0x5605bb911880 (GVfsBackendTrash)
trash: Queued new job 0x5605bb912820 (GVfsJobMount)
trash: send_reply(0x5605bb912820), failed=0 ()
trash: backend_dbus_handler org.gtk.vfs.Mount:CreateFileMonitor (pid=64556)
trash: Queued new job 0x5605bb912b80 (GVfsJobCreateMonitor)
trash: send_reply(0x5605bb912b80), failed=0 ()
trash: backend_dbus_handler org.gtk.vfs.Mount:CreateFileMonitor (pid=64556)
trash: Queued new job 0x5605bb912b80 (GVfsJobCreateMonitor)
trash: send_reply(0x5605bb912b80), failed=0 ()
trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=64556)
trash: Queued new job 0x5605bb8fab50 (GVfsJobQueryInfo)
trash: send_reply(0x5605bb8fab50), failed=0 ()
trash: backend_dbus_handler org.gtk.vfs.Mount:QueryInfo (pid=64556)
trash: Queued new job 0x5605bb8fabf0 (GVfsJobQueryInfo)
trash: send_reply(0x5605bb8fabf0), failed=0 ()
dav: Added new job source 0x561106bad0c0 (GVfsBackendDav)
dav: Queued new job 0x561106ba5ab0 (GVfsJobMount)
dav: + mount
dav: + soup_authenticate (interactive, first auth) 
dav:  [/remote.php/dav/files/fs] webdav: 1, collection 1 [res: 1]
^C

(Before I terminated gvfsd, the error message appeared in nautilus (as reporter mentioned).

abrt reports with gvfs 1.50, maybe some fallout from soup3 migration in gvfs?

https://retrace.fedoraproject.org/faf/problems/bthash/?bth=efb4683b1277d102ce2484221776ecb0879a2ff9&bth=3614e2999efb2891afa149de1c93730e490b661b&bth=4112af31345e0c5ab4f57c6d92e64391bb7aa6a0&bth=d2b5951f0e50c350e93c980e74926ee3c0c77762&bth=677894f8e88c9bc77abb7fc05ab0a8064c54aee1&bth=227695c525e21aed8ea27de2c6f0d96718fe9746&bth=bbf3f288d36db6c4420b1e50dde170d7a956732f&bth=e13bfd6ce7f5a50d37e30fe53c3b3f7142a30f5e&bth=ac5769b4a07816d3286edada853c94f4dafddfec&bth=11f97516e8a99df7003b2ab82d3432dbe5ebe2d5

Comment 6 Felix Schwarz 2022-08-19 10:36:05 UTC
Interestingly I CAN connect to my NextCloud instance when starting gvfs with "GVFS_HTTP_DEBUG=all". The logs contain some cookie values which I'm hesitant to share publicly but I noticed one additional assertion where previously the process would crash:

(process:65023): GVFS-CRITICAL **: 12:31:47.663: g_mount_spec_set_with_len_internal: assertion 'value != NULL' failed
dav: send_reply(0x55f21a0e4a70), failed=0 ()
...

Comment 7 Felix Schwarz 2022-08-19 10:42:45 UTC
I guess this is an upstream problem so I created an upstream issue: https://gitlab.gnome.org/GNOME/gvfs/-/issues/644

Comment 8 Felix Schwarz 2023-04-03 09:42:48 UTC
Fixed in libsoup 3.3.1+ (F38 at the moment)

Comment 9 Felix Schwarz 2023-04-03 09:44:52 UTC
David: Any chance we could get libsoup 3.3.1 in F37? Or should I try to backport this exact commit for libsoup3 in F37?

Comment 10 Fedora Update System 2023-04-04 21:15:24 UTC
FEDORA-2023-a2dd5b1351 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a2dd5b1351

Comment 11 Fedora Update System 2023-04-05 02:39:56 UTC
FEDORA-2023-a2dd5b1351 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a2dd5b1351`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a2dd5b1351

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Albert Flügel 2023-04-05 19:07:19 UTC
Indeed, with this bunch installed davs to nextcloud works again.

Comment 13 Fedora Update System 2023-04-06 01:54:31 UTC
FEDORA-2023-a2dd5b1351 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.