*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097
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.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1727408/+attachment/4994758/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1727408/+attachment/4994760/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1727408/+attachment/4994763/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1727408/+attachment/4994764/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1727408/+attachment/4994765/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1727408/+attachment/4994766/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1727408/+attachment/4994767/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 1706097
gvfsd-mtp crashed with SIGSEGV
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1727408
Title:
gvfsd-mtp crashed with SIGSEGV (Google Pixel, Android 8.0.0, 10/5
security patch)
Status in gvfs package in Ubuntu:
New
Bug description:
The auto-launch of the MTP service fails when connecting my Google
Pixel running Android 8.0.0 and the October 5 security patch. I don't
notice anything but the crash reporting appearing sometime after I
connect my phone - I'm mostly tethering, which works perfectly.
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: Wed Oct 25 08:49:27 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2017-10-12 (12 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/1
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
SegvAnalysis:
Segfault happened at: 0x7f0d2684e5a9: mov 0x18(%rax),%rax
PC (0x7f0d2684e5a9) 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/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-18 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1727408/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
