gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
shown this bug after a reboot
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gvfs-backends 1.40.1-1
ProcVersionSign
Uname: Linux 5.0.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 22 22:20:41 2019
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2019-06-18 (8 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f9d2ed570c7 <__strlen_avx2+55>: vpcmpeqb (%rdi),%ymm0,%ymm1
PC (0x7f9d2ed570c7) ok
source "(%rdi)" (0x5cf80ea0) not located in a known VMA region (needed readable region)!
destination "%ymm0" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
__strlen_avx2 () at ../sysdeps/
?? () from /lib/x86_
?? () from /lib/x86_
LIBMTP_
LIBMTP_
Title: gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf vboxusers
separator:
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 #1724075, 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.