gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()

[digc16]

Uploaded pictures to computer. Went to the picture's file to open up a picture. Image Viewer crashed and generated this report.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Mon Jul 15 09:38:46 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationDate: Installed on 2013-06-10 (34 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130609)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.4 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f53c1f4db04 <g_object_unref+20>: cmpq $0x50,(%rax)
 PC (0x7f53c1f4db04) 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: No upgrade log present (probably fresh install)
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 #1200499, 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.