gvfsd-obexftp crashed with SIGSEGV in dbus_message_get_reply_serial()

[Mohamad Putra Maghribi]

I got this crash message when try to browse files on bluetooth device using blueman-browse --device=xx:xx:xx:xx:xx:xx. It looks similar to this bug: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1054385 but with different error message summary.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.16.0-1ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Wed Apr 3 12:06:20 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-obexftp
InstallationDate: Installed on 2013-03-20 (13 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 (20130313)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-obexftp --spawner :1.6 /org/gtk/gvfs/exec_spaw/6
SegvAnalysis:
 Segfault happened at: 0x7f839449d7c3: movzbl (%rax),%eax
 PC (0x7f839449d7c3) ok
 source "(%rax)" (0x0000005b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: gvfsd-obexftp crashed with SIGSEGV in dbus_message_get_reply_serial()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data

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