gvfsd-mtp crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I haven't even activated MTP on the phone I attached.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gvfs-backends 1.36.1-0ubuntu1.1
ProcVersionSign
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 5 17:31:57 2018
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-10-13 (388 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f653438358a: mov 0x18(%r12),%rax
PC (0x7f653438358a) ok
source "0x18(%r12)" (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/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-06-25 (133 days ago)
UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo
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.