gvfsd-mtp crashed with SIGSEGV

Bug #1726468 reported by Wellington Torrejais da Silva
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

gvfsd-mtp crashed with SIGSEGV

When phone start connected to the PC

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 23 13:54:50 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2016-08-02 (446 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.2 /org/gtk/gvfs/exec_spaw/9
ProcEnviron:
 LANG=pt_BR.utf8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f40a37af5a9: mov 0x18(%rax),%rax
 PC (0x7f40a37af5a9) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

Revision history for this message
Wellington Torrejais da Silva (wellington1993) wrote :
information type: Private → Public
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.

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.