gvfsd-mtp crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
It appeared after a while on the nautilus.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.33.91-0ubuntu1
ProcVersionSign
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Sep 11 11:33:34 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-02-17 (205 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f7d532235a9: mov 0x18(%rax),%rax
PC (0x7f7d532235a9) 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/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-06-02 (101 days ago)
UserGroups: adm cdrom dialout dip games libvirt lpadmin plugdev sambashare sudo vboxusers
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.