Bug#597133: gvfsd-dav crashes, resulting in "Message did not receive a reply"

[Fabian Greffrath]

Am Donnerstag, den 13.03.2014, 11:30 +0000 schrieb Simon McVittie: 
> Ah, right. So the bug here might be: you are using an incorrect form of
> the non-standard dav+sd:// URL (I wonder whether it's documented
> anywhere?), the expected result is graceful failure with an error
> message, and the actual result is a crash.

Erm, no, it doesn't crash anymore.

> Can you still reproduce this failure mode through a GUI like Nautilus?
> (If you can, then there might be a second bug: "the GUI uses the wrong
> form of dav+sd:// too".)

Well, that's really strange:

If I enable user file sharing in g-c-c, the GUI tells me that my shared
folder is now accessible to other computers under the "dav://kff50"
address (kff50 is my hostname). Note that it does neither add the '+sd'
part nor tell the port that it has opened.

Now I open Nautilus and choose "Connect to Server". If I paste the
address that g-c-c just suggested, Nautilus presents an error message:
"Oops! Something went wrong.
Unhandled error message: HTTP-Fehler: Cannot connect to destination
(kff50)"

The same does gvfs-mount in a terminal:
$ LANG=C gvfs-mount dav://kff50
Error mounting location: HTTP-Fehler: Cannot connect to destination
(kff50)

However, if I add the port opened by apache to the command line, it
works as expected:
$ LANG=C gvfs-mount dav://kff50:50211
$ echo $?
0

Now Nautilus does indeed show "kff50:50211" as a shortcut in the Network
section of its sidebar.

> That would probably be useful - having a backtrace is always better than
> having no backtrace.

I can provide one later.

- Fabian