gvfsd-dav crashed with SIGSEGV in g_closure_invoke()

Bug #1737278 reported by Julian Andres Klode
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

It seems that gvfsd-dav crashed. I played with it when connecting to a dav created by enabling file sharing on the local machine. I turned it off, it must have crashed after that, but I only got the report now.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gvfs-backends 1.34.1-1ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.8-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Dec 9 01:11:06 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-dav
InstallationDate: Installed on 2017-12-08 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/gvfs/gvfsd-dav --spawner :1.15 /org/gtk/gvfs/exec_spaw/12
SegvAnalysis:
 Segfault happened at: 0x560529675aad: mov (%rax),%rax
 PC (0x560529675aad) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfsd-dav crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to bionic on 2017-12-08 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Julian Andres Klode (juliank) wrote :
information type: Private → Public
Revision history for this message
Julian Andres Klode (juliank) wrote :

There did not seem to be anything private in the coredump, hence marking as public.

tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.