gvfsd-mtp crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
happened when the phone was connected to the computer
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gvfs-backends 1.34.1-1ubuntu4
Uname: Linux 4.15.0-
ApportVersion: 2.20.8-0ubuntu3
Architecture: amd64
Date: Wed Dec 13 21:55:59 2017
ExecutablePath: /usr/lib/
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7effcccdb5a9: mov 0x18(%rax),%rax
PC (0x7effcccdb5a9) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo
information type: | Private → Public |
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.