gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()

[iMac]

I was importing photos in Shotwell from my Android phone.

I went to Open the folder on the phone from the Unity panel, and this crash occurred.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 7 09:05:15 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.6 /org/gtk/gvfs/exec_spaw/6
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7f6402811b84 <g_object_unref+20>: cmpq $0x50,(%rax)
 PC (0x7f6402811b84) ok
 source "$0x50" ok
 destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_object_unref () 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
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
Title: gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()
UpgradeStatus: Upgraded to saucy on 2013-09-03 (3 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse kismet libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vboxusers vde2-net video

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