gvfsd-mtp crashed with SIGSEGV in weak_refs_notify()

[Ante Karamatić]

I plugged in the phone, nautilus windows popped out. It had my phone preselected from the menu, but nothing was showing up. After some time I've unlocked the screen - not sure if that's related, but content showed up. I have then unmounted the mountpoint and remounted it again. I'm not sure at what time crash happened.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
CheckboxSubmission: dfc057e825a9177f1e0355d98003b324
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Fri Mar 15 07:56:22 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2011-09-14 (547 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110914)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.4 /org/gtk/gvfs/exec_spaw/2
SegvAnalysis:
 Segfault happened at: 0x7f0e9a8510bc: mov 0x20(%rax),%rax
 PC (0x7f0e9a8510bc) 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
 weak_refs_notify (data=0x7f0e8800e030) at /build/buildd/glib2.0-2.35.8/./gobject/gobject.c:2470
 g_object_unref (_object=0x956830) at /build/buildd/glib2.0-2.35.8/./gobject/gobject.c:2987
 g_value_unset (value=value@entry=0x7fff0416bd20) at /build/buildd/glib2.0-2.35.8/./gobject/gvalue.c:274
 g_signal_emit_valist (instance=0x956830, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff0416bf68) at /build/buildd/glib2.0-2.35.8/./gobject/gsignal.c:3344
Title: gvfsd-mtp crashed with SIGSEGV in weak_refs_notify()
UpgradeStatus: Upgraded to raring on 2013-03-15 (0 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare 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 #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.