gvfsd-mtp crashed with SIGSEGV in g_object_unref()

[Rainer Rohde]

Not sure what caused this, but I was unplugging or plugging in my Nexus7

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Fri Feb 22 10:08:17 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.8 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fdb292f20bc: mov 0x20(%rax),%rax
 PC (0x7fdb292f20bc) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[crtm (carlosrtm)]

Chras when plugging or unplugging my Samsung Galaxy S2

[crtm (carlosrtm)]

here a temporarily trick:
http://www.webupd8.org/2012/12/how-to-mount-android-40-ubuntu-go-mtpfs.html

[Thomas Hotz (thotz-deactivatedaccount)]

I have reported a similar bug see #1130101.
​​

[Philip Langdale (langdalepl)]

It's the same bug. The retracing bot will identify them as dupes when it finally gets around to processing them.

This one's a bit weird, but until I see the re-traced backtrace I can't tell what's really going on, but it looks an awful lot like a bug that should have been fixed in 1.15.3, so I'm puzzled to see it show up with that version.

[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.