gvfsd-mtp crashed with SIGSEGV in libusb_bulk_transfer()

[Achim Behrens]

uptodate 13.04
connected my nexus4 and transfered some files. when selecting to unmount (with the little eject arrow on the left side of nautilus) nautilus didnt respont. after that apport startet.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.16.0-1ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sat Mar 30 22:46:33 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2011-10-29 (518 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.4 /org/gtk/gvfs/exec_spaw/4
SegvAnalysis:
 Segfault happened at: 0x7f258ba9e5d0: mov 0x30(%rax),%rdi
 PC (0x7f258ba9e5d0) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () 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
 LIBMTP_Read_Event () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 ?? ()
Title: gvfsd-mtp crashed with SIGSEGV in libusb_bulk_transfer()
UpgradeStatus: Upgraded to raring on 2013-02-24 (34 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #1121285, 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.