gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage()

[shankao]

While deleting some files from my phone. I think I could have disconnected it to early

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Thu Sep 5 13:59:12 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2012-11-25 (284 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.4 /org/gtk/gvfs/exec_spaw/8
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_SG:en
 LANG=en_SG.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f277c000078: add %ah,0x8(%rax)
 PC (0x7f277c000078) in non-executable VMA region: 0x7f277c000000-0x7f277c090000 rw-p None
 source "%ah" ok
 destination "0x8(%rax)" (0x00000009) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing writable VMA None
 writing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 LIBMTP_Get_Storage () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage()
UpgradeStatus: Upgraded to saucy on 2012-11-25 (284 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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