gvfsd-mtp crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Mine crashed on shut down. When I restarted the computer hesitated and was not responding well. Sluggish and would not function until I submitted a report.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Oct 30 20:12:14 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-01-15 (288 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f41bbd895a9: mov 0x18(%rax),%rax
PC (0x7f41bbd895a9) 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:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-20 (10 days ago)
UserGroups: adm cdrom dip 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.