Cannot enable bluetooth

Bug #1521737 reported by Pat McGowan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
Pat McGowan
bluez (Ubuntu)
Fix Released
Undecided
Simon Fels

Bug Description

MX4 running propsoed 181 with debug enabled kernel

Paired to car and saw signal strength indicated
Left car, renetered car and noticed not paried and BT disabled in the indicator
tried to enable, 1 min later it resets to disabled

Bluetoothd is no longer running
there was a previous crash file in /var/crash

see syslog attached

/var/lib/urfkill/saved-states:
[BLUETOOTH]
soft=false
prev-soft=false

/var/log/upstart/bluetooth-touch.log
start: Unknown job: bluetooth-touch-arale

Reboot and bt is enabled

Tags: bluez-touch
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :
Changed in bluez (Ubuntu):
assignee: nobody → Simon Fels (morphis)
description: updated
description: updated
description: updated
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Log reports
Dec 1 09:25:00 ubuntu-phablet bluetoothd[744]: Not enough free handles to register service

so we may have new FH leaks

Changed in canonical-devices-system-image:
status: New → Confirmed
assignee: nobody → Pat McGowan (pat-mcgowan)
Revision history for this message
Simon Fels (morphis) wrote :

@Pat: No that is not a file descriptor leak. That is just an internal handle not related to any file descriptors to store GATT related attributes. This due to some unconverted profiles after API/infrastructures changes and known upstream. Ignore that.

Also ignore that there is no bluetooth-touch-arale job. That is not needed on arale and therefor doesn't exist.

Revision history for this message
Simon Fels (morphis) wrote :

It would be awesome if you get the crash file from /var/crash/_usr_lib_bluetooth_bluetoothd.0.crash and could send it to me.

Revision history for this message
Simon Fels (morphis) wrote :

Examined the crash file I got from Pat:

#0 strlen () at ../sysdeps/arm/armv6t2/strlen.S:85
85 ../sysdeps/arm/armv6t2/strlen.S: No such file or directory.
(gdb) bt
#0 strlen () at ../sysdeps/arm/armv6t2/strlen.S:85
#1 0xb6f13ebc in avrcp_handle_media_player_list (session=0xb8f339c0,
    session=0xb8f339c0, end_item=<optimized out>, start_item=<optimized out>,
    pdu=0xb8f43283) at profiles/audio/avrcp.c:1917
#2 avrcp_handle_get_folder_items (session=0xb8f339c0, pdu=0xb8f43283,
    transaction=<optimized out>) at profiles/audio/avrcp.c:1968
#3 0xb6f13fb8 in handle_browsing_pdu (conn=<optimized out>,
    transaction=<optimized out>, operands=0xb8f43283 "q\b",
    operand_count=<optimized out>, user_data=0xb8f339c0)
    at profiles/audio/avrcp.c:2028
#4 0xb6f0f088 in session_browsing_cb (chan=<optimized out>,
    cond=<optimized out>, data=0xb8f3ba28) at profiles/audio/avctp.c:930
#5 0xb6e19e90 in g_main_dispatch (context=0xb8f28100)
    at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122
#6 g_main_context_dispatch (context=context@entry=0xb8f28100)
    at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737
#7 0xb6e1a114 in g_main_context_iterate (context=0xb8f28100,
    block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808
#8 0xb6e1a3b0 in g_main_loop_run (loop=0xb8f28030)
    at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:4002
#9 0xb6efef3e in main (argc=1, argv=0xbebdde04) at src/main.c:661

Its crashing because the endpoint didn't assigned any valid name. Could be a race condition but needs further investigation.

Revision history for this message
Simon Fels (morphis) wrote :

Have a fix for the crash. Uploading a new bluez package to silo 9.

Simon Fels (morphis)
Changed in bluez (Ubuntu):
status: New → In Progress
Changed in canonical-devices-system-image:
status: Confirmed → Fix Committed
importance: Undecided → High
milestone: none → ww02-2016
Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
tags: added: bluez-touch
Changed in bluez (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.