gvfsd-mtp crashed with SIGSEGV

Bug #1698716 reported by Till Kamppeter
This bug report is a duplicate of:  Bug #1706097: gvfsd-mtp crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Happens every time when I connect my Android smartphone to the USB for charging its battery.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Jun 18 23:57:22 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (781 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f98f63fbcc9: mov 0x18(%rax),%rax
 PC (0x7f98f63fbcc9) 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-04-14 (65 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark

Revision history for this message
Till Kamppeter (till-kamppeter) 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 #1689770, 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.

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.