upstream bug comment "This crash can only happen if something is trying to use libsoup to request a URI that (a) has no hostname, and (b) is not http or https.
"???" I've fixed libsoup to be pickier about the URIs it accepts. But this might just push the crash to somewhere else in gvfsd-http. (Previously soup_message_new_with_uri() would never fail, even if you passed a completely bogus URI. Now it can return NULL.) Another possibility is that it's the webdav server's fault, because it's returning a totally broken redirect like: HTTP/1.1 301 Moved Permanently Location: C:\Documents and Settings\blah\blah Previously, that would have triggered this crash. Now it will just cause the message to finish with status SOUP_STATUS_MALFORMED. Reassigning back to gvfs and NEEDINFO'ing, since there's still going to be *something* wrong when the reporter tries the new libsoup." could you try using the new version? ** Changed in: gvfs (Ubuntu) Status: Triaged => Incomplete -- gvfsd-http crashed with SIGSEGV in soup_str_case_hash() https://bugs.launchpad.net/bugs/216763 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs