gvfsd-mtp crashed with SIGSEGV

Bug #1723486 reported by Michael Thayer
This bug report is a duplicate of:  Bug #1706097: gvfsd-mtp crashed with SIGSEGV. Edit Remove
6
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Found in /var/crash, not sure exactly when this happened.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 17:08:35 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2016-05-31 (500 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 /org/gtk/gvfs/exec_spaw/4
SegvAnalysis:
 Segfault happened at: 0x7f52e13eb5a9: mov 0x18(%rax),%rax
 PC (0x7f52e13eb5a9) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-05 (8 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo vboxusers

Revision history for this message
Michael Thayer (michael-thayer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1706097, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.