gvfsd-mtp crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Same error again
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gvfs-backends 1.34.1-1ubuntu4
ProcVersionSign
Uname: Linux 4.14.0-3-generic x86_64
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Mon Dec 18 17:30:23 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-08-02 (502 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f86cc3735a9: mov 0x18(%rax),%rax
PC (0x7f86cc3735a9) 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 bionic on 2017-11-24 (24 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf
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.