gvfsd-mtp crashed with SIGSEGV in g_object_unref() after "ejecting" device

[ariel cornejo]

I experienced this right after "ejecting" my Samsung Galaxy S III in Nautilus (I had just copied a 733 MB file)

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.4-0ubuntu1b1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Mon Mar 18 01:54:40 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2012-11-05 (132 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.11 /org/gtk/gvfs/exec_spaw/7
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f73a37cb0bc: mov 0x20(%rax),%rax
 PC (0x7f73a37cb0bc) ok
 source "0x20(%rax)" (0xaaaaaaaaaaaaaaca) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_value_unset () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV in g_object_unref()
UpgradeStatus: Upgraded to raring on 2013-03-13 (5 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[ariel cornejo (arielco)]

Possibly related to #1130101 ?

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