gvfsd-mtp crashed with SIGSEGV in libusb_submit_transfer()

[Darren Lachambre]

I was putting books on my Kobo Arc and when I clicked on the eject button in Nautilus I had the error. The books didn't make it on, either.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
Uname: Linux 3.11.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Sun Sep 8 12:19:11 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2013-09-03 (5 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.16 /org/gtk/gvfs/exec_spaw/5
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ff4be355b63 <libusb_submit_transfer+35>: mov 0x30(%rax),%r13
 PC (0x7ff4be355b63) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%r13" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 libusb_submit_transfer () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 libusb_bulk_transfer () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
Title: gvfsd-mtp crashed with SIGSEGV in libusb_submit_transfer()
UpgradeStatus: Upgraded to saucy on 2013-09-07 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1152997, 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.