Bluetooth panel not getting scan results

Bug #1234361 reported by Pat McGowan
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
lxc-android-config (Ubuntu)
Fix Released
High
Sergio Schvezov
ubuntu-system-settings (Ubuntu)
Invalid
High
Unassigned

Bug Description

Mako running build 76

The scan does not detect the bluetooth headset.
hcitool scan does find it

Scanning ...
 00:18:16:20:00:FE RF-MAB2
 10:40:F3:7E:12:B1 ubuntu-0

bt-monitor output is (note the Name and Alias and the Glib assertion)

[Adapter: ubuntu-phablet-0 (98:D6:F7:31:C6:A6)] Device found:
[00:18:16:20:00:FE]

(bt-monitor:4149): GLib-GObject-CRITICAL **: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
  Name: (null)
  Alias: 00-18-16-20-00-FE
  Address: 00:18:16:20:00:FE
  Icon: audio-card
  Class: 0x240404
  LegacyPairing: 0
  Paired: 0
  RSSI: -58

bt-monitor on desktop:

[Adapter: pat-samsung-0 (88:53:2E:1B:4C:D3)] Device found:
[00:18:16:20:00:FE]
  Name: RF-MAB2
  Alias: RF-MAB2
  Address: 00:18:16:20:00:FE
  Icon: audio-card
  Class: 0x240404
  LegacyPairing: 1
  Paired: 0
  RSSI: -48

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Tested with a RocketFish (BT v2.1) and Logitech FreePulse (BTv2.0)

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Ran system-settings on the desktop and it did not find the device in the scan
For the record, the standard UI on desktop does find the device every time.

Changed in ubuntu-system-settings (Ubuntu):
assignee: nobody → Charles Kerr (charlesk)
importance: Undecided → High
Revision history for this message
Dave Morley (davmor2) wrote :

This works correctly if you make your device writeable. Once it writes the config it will then connect in Readonly mode. I'm assuming therefore that the config path is something like /etc/bluez/x.conf or something similar and has no write access to that file so can't set the devices up.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-system-settings (Ubuntu):
status: New → Confirmed
Dave Morley (davmor2)
tags: added: avengers qa-touch
Revision history for this message
Scott Sweeny (ssweeny) wrote :

I was able to pair a bluetooth headset with my maguro by adding /var/lib/bluetooth to my writable-paths file.

It should be noted that this directory doesn't exist on first boot but was created at boot time after I enabled a writable image in order to edit the paths file.

Inside of this directory is a subdirectory with (I presume) the MAC address of the bluetooth adapter that contains various data including devices that have been/are paired with it.

Changed in ubuntu-system-settings (Ubuntu):
assignee: Charles Kerr (charlesk) → Oliver Grawert (ogra)
Oliver Grawert (ogra)
Changed in lxc-android-config (Ubuntu):
status: New → Confirmed
assignee: nobody → Oliver Grawert (ogra)
importance: Undecided → High
Changed in ubuntu-system-settings (Ubuntu):
status: Confirmed → Invalid
assignee: Oliver Grawert (ogra) → nobody
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

I can confirm that creating the dir and adding it to the writable-paths file allow me to scan and connect.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Once connected there are issues, no sound is routed to the headset, and bluetoothd is at 100% cpu

Revision history for this message
Dave Morley (davmor2) wrote :

No setup of bluetooth devices is still in place on Maguro Trusty image 14

Changed in lxc-android-config (Ubuntu):
assignee: Oliver Grawert (ogra) → Sergio Schvezov (sergiusens)
Changed in lxc-android-config (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxc-android-config - 0.124

---------------
lxc-android-config (0.124) trusty; urgency=low

  * Adding /var/lib/bluetooth to writeable persistent paths. (LP: #1234361)
  * Adding /var/lib/lightdm to writeable temporary paths.
  * Fixed syntax-error-in-debian-changelog warnings to get UDD working again.
  * Removing accidentally added grep file.
 -- Sergio Schvezov <email address hidden> Fri, 13 Dec 2013 14:28:00 -0500

Changed in lxc-android-config (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Needs a bluez package change to create the /var/lib/bluetooth folder in the image at install time.

Changed in bluez (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
importance: Undecided → High
status: New → Confirmed
Changed in bluez (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluez - 4.101-0ubuntu10

---------------
bluez (4.101-0ubuntu10) trusty; urgency=low

  * debian/patches/telephony_ofono_add_watch.patch: fix telephony-ofono code
    to have the add_watch function not be conditioned out, since it's used.
  * debian/rules: explicitly specify to use ofono a the telephony service.
  * debian/bluez.dirs: add /var/lib/bluetooth, we need to have it created
    on Ubuntu Touch so that discovery writes cache data for classes, seen
    addresses, etc. (LP: #1234361)
 -- Mathieu Trudel-Lapierre <email address hidden> Thu, 19 Dec 2013 21:36:00 -0500

Changed in bluez (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Dave Morley (davmor2) wrote :

Confirming this is now fixed for me on maguro

I will file a new bug for the fact that my headset doesn't work :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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