bluetooth-sendto crashed with SIGSEGV in g_path_is_absolute()

[Patrik B.]

The application gave this error while sending files to a Blackberry Q10 phone via Bluetooth.

NOTE, that there might be previously reported similar bugs but for older, unsupported versions of Ubuntu, hence I'm reporting this as a new issue.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gnome-bluetooth 3.8.2.1-0ubuntu12
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jul 8 10:43:25 2015
ExecutablePath: /usr/bin/bluetooth-sendto
InstallationDate: Installed on 2015-07-05 (2 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: bluetooth-sendto --device=94:EB:CD:C6:D1:B1 --name=BLACKBERRY-75C5
SegvAnalysis:
 Segfault happened at: 0x7efbf6a45167 <g_path_is_absolute+7>: cmpb $0x2f,(%rdi)
 PC (0x7efbf6a45167) ok
 source "$0x2f" ok
 destination "(%rdi)" (0x000000d0) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 g_path_is_absolute () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 ?? ()
Title: bluetooth-sendto crashed with SIGSEGV in g_path_is_absolute()
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 #753079, 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.