gvfsd-gphoto2 crashed with SIGABRT in raise()

[Typhoe]

Hi,

this crash occurs when I connect my android phone Samsung Galaxy S3.
My phone is set in mtp mode.

Sep 3 09:42:42 typhoe-OptiPlex-780 kernel: [ 70.376144] usb 1-4.2: new high-speed USB device number 5 using ehci_hcd
Sep 3 09:42:42 typhoe-OptiPlex-780 kernel: [ 70.469062] usb 1-4.2: New USB device found, idVendor=04e8, idProduct=6860
Sep 3 09:42:42 typhoe-OptiPlex-780 kernel: [ 70.469067] usb 1-4.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Sep 3 09:42:42 typhoe-OptiPlex-780 kernel: [ 70.469070] usb 1-4.2: Product: GT-I9300
Sep 3 09:42:42 typhoe-OptiPlex-780 kernel: [ 70.469072] usb 1-4.2: Manufacturer: samsung

Just before I plugged the phone, I added a rule to udev (and restarted it):
/etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{IDPRODUCT}=="6860", MODE="0666", GROUP="plugdev"

regards.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-backends 1.13.7-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Mon Sep 3 11:18:04 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120830)
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: gvfsd-gphoto2 crashed with SIGABRT in raise()
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 #984993, 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.