← Back to team overview

kernel-packages team mailing list archive

[Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester


The Ubuntu System Settings log contains such a warning:

14:15:08,530 - WARNING - file:///usr/share/ubuntu/settings/system/qml-
plugins/bluetooth/DevicePage.qml:156: TypeError: Cannot read property
'paired' of null

This corresponds to the pairing request that has been issued at the same

14:15:08 ubuntu-phablet bluetoothd[2278]:
src/device.c:bonding_request_new() Requesting bonding for

Which basically means that the user has clicked one of the discovered
devices on the devices list. This triggers the pairing request.

The error from the Ubuntu System Settings also means that the
selectedDevice property has not been properly updated. This is set based
on the device address and the query goes down to the devices model
settings/trunk/view/head:/plugins/bluetooth/devicemodel.cpp#L564. And it
can fail only if there is no device of such address on an internal
devices list. This list is updated with addDevice() call

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.

  Cannot pair mako with 2014 Subaru Forester

Status in Canonical System Image:
Status in bluez package in Ubuntu:

Bug description:
  Since the bluez5 transition my mako has not been able to pair with the
  radio in my 2014 Subaru Forester. When the radio is put into pairing
  mode the phone sees the CAR_M_MEDIA device, but when I click "connect"
  the radio immediately shows "failed" and no PIN prompt is shown on the
  phone. Additionally, the entry in system-settings for the car stereo
  is left in a limbo state with the "forget" button inactive. The only
  way to remove the entry is to use bluetoothctl from the command line.

  Here's what the phone is currently running:
  current build number: 252
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-02 00:31:33
  version version: 252
  version ubuntu: 20160302
  version device: 20160112
  version custom: 20160201-5-vivid

To manage notifications about this bug go to: