Bug 733875 – Crashs with "Code should not be reached" in OBEX Bluetooth

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 733875 - Crashs with "Code should not be reached" in OBEX Bluetooth


Summary:	Crashs with "Code should not be reached" in OBEX Bluetooth


Status:	RESOLVED DUPLICATE of bug 733891

Product:	folks
Classification:	Platform
Component:	BlueZ backend
Version:	git master
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	Unset
Assigned To:	folks-maint
QA Contact:	folks-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2014-07-28 16:07 UTC by Christian Bürckert
Modified:	2014-08-11 14:22 UTC

See Also:
GNOME target:	---
GNOME version:	3.13/3.14

Attachments
Installed Packages with Versions (104.59 KB, text/plain) 2014-07-31 20:20 UTC, Christian Bürckert	Details

Description Christian Bürckert 2014-07-28 16:07:16 UTC

This happens everytime you start the application and bluetooth is on and a smartphone is paired and in range. Shortly before the application crashes the mobile tells "Computer wants to access contact list". 

Here is the detailed Exception from the terminal:
bluez:ERROR:bluez-persona-store.c:2645:_folks_backends_blue_z_persona_store_perform_obex_transfer_co: code should not be reached


Here is the gdb backtrace:
(gdb) backtrace

+ Trace 233888

#0 raise
from /usr/lib/libc.so.6
#1 abort
from /usr/lib/libc.so.6
#2 g_assertion_message
from /usr/lib/libglib-2.0.so.0
#3 g_assertion_message_expr
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/folks/42/backends/bluez/bluez.so
#5 g_simple_async_result_complete
from /usr/lib/libgio-2.0.so.0
#6 ??
from /usr/lib/libgio-2.0.so.0
#7 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#8 ??
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#10 g_application_run
from /usr/lib/libgio-2.0.so.0
#11 _vala_main
#12 __libc_start_main
from /usr/lib/libc.so.6
#13 _start

Comment 1 Erick Perez Castellanos 2014-07-31 16:05:21 UTC

Could you provide more details? The platform and versions of the complete bluetooth stack, folks and gnome-contacts, and evolution-data-server as well

Comment 2 Christian Bürckert 2014-07-31 20:20:45 UTC

Created attachment 282201 [details]
Installed Packages with Versions

Comment 3 Christian Bürckert 2014-07-31 20:24:16 UTC

OS: Arch Linux multilib
Kernel: 3.15.5-2-ARCH

local/bluez 5.21-2
local/bluez-libs 5.21-2
local/bluez-utils 5.21-2
local/gnome-shell 3.12.2-1 (gnome)
local/gnome-shell-extensions 3.12.2-1 (gnome)
local/evolution 3.12.4-1 (gnome-extra)
local/evolution-data-server 3.12.4-1
local/folks 0.9.7.1-1
local/gnome-contacts 3.12.0-1 (gnome)

Comment 4 voidbreak 2014-08-05 01:41:45 UTC

The conflict seems to occur when bluez attempts to pull contact and phone history data from my phone.

After I unpair my phone and pair the phone again, Empathy has no issues running. It's when I give bluez access to my phone book that Empathy crashes and no longer works. The phone notification in question is "Phone book access request" with the message saying my computer "wants to access your contacts and call history". As soon as I accept, Empathy crashes.

Comment 5 b745uvdmpm 2014-08-08 18:47:54 UTC

It seems to be fixed by https://git.gnome.org/browse/folks/commit/?id=5280f3363eb1abd782d25dfdcad33f01958bdb1c
See also #733891

Comment 6 Philip Withnall 2014-08-11 14:22:02 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 733891 ***