gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()

Bug #1724075 reported by Richard Walker
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I was transferring a download to my android when then notice came up.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 16 15:41:45 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2017-10-13 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 /org/gtk/gvfs/exec_spaw/12
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7ff9a80718a7 <__strlen_avx2+55>: vpcmpeqb (%rdi),%ymm0,%ymm1
 PC (0x7ff9a80718a7) ok
 source "(%rdi)" (0x59dc5460) 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/x86_64/multiarch/strlen-avx2.S:93
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 LIBMTP_Get_Filemetadata () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 LIBMTP_Get_Files_And_Folders () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
Title: gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()
UpgradeStatus: Upgraded to artful on 2017-10-15 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Richard Walker (richardlee5) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:93
 ptp_unpack_PTPTIME (str=0x59dc5469 <error: Cannot access memory at address 0x59dc5469>) at ptp-pack.c:646
 ptp_object_want (params=params@entry=0x7ff98c01c930, handle=1, want=want@entry=5, retob=retob@entry=0x7ff99f7fdc70) at ptp.c:6772
 LIBMTP_Get_Filemetadata (device=device@entry=0x7ff98c0216d0, fileid=<optimized out>) at libmtp.c:4351
 LIBMTP_Get_Files_And_Folders (device=device@entry=0x7ff98c0216d0, storage=<optimized out>, parent=<optimized out>) at libmtp.c:4532

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
tags: added: eoan
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.