Ubuntu Touch is no longer supported.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858
Title:
[bluetooth]
** Changed in: canonical-devices-system-image
Assignee: John McAleely (john.mcaleely) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858
Title:
[bluetooth]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Note, I forgot to mention in the previous comment that on xenial
desktop, the PIN wasn't displayed in settings.
Finally, here's the trace from my krillin, running rc-proposed/bq-
aquaris.en #270 + bluez 5.37. Same result as the original bug
description.
** Attachment added: "btmon trace"
And here's the trace for my xenial desktop running on a Thinkpad 410s.
** Attachment added: "btmon trace"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4593245/+files/xenial-desktop.cap
--
You received this bug notification because you are a member of
OK, so I guess I was wrong about pairing working with my Ubuntu desktops
( both running 5.37 ), although I'm pretty sure this worked for me
before. Maybe I was running bluez 5.36 when I tested?
Here's a btmon trace of wily running bluez 5.37 on a mid '13 macair. I
get prompted to view the PIN
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => John McAleely (john.mcaleely)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@Simon
Re: comment #6, when I paired the keyboard with my Ubuntu laptops,
neither prompted me at all; the keyboard silently paired and was usable.
That said, I'll re-test this afternoon and get you the HCI dump from the
phone.
--
You received this bug notification because you are a member of
@Tony: Can you reproduce this once again and record the HCI packets by
running
$ sudo btmon -w test.cap
Then attach test.cap here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858
Just as a additional note: The actual pairing method is selected in the
kernel. See
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/smp.c#n859
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
And there we go:
Mar 7 15:08:44 ubuntu-phablet bluetoothd[890]: src/device.c:new_auth()
Requesting agent authentication for 04:69:F8:C2:A0:09
Mar 7 15:08:44 ubuntu-phablet bluetoothd[890]: src/agent.c:agent_ref()
0xb8c78950: ref=3
Mar 7 15:08:44 ubuntu-phablet bluetoothd[890]:
Because what pairing method is selected is chosen further down the stack
so settings only reacts on what bluez tells it should do. I suspect the
keyboard uses pairing capability KeyboardOnly which then should lead to
passkey entry where the initiator displays and the responder inputs the
PIN (we
** Attachment added: "dbus log from krillin"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591780/+files/dbus.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Description changed:
Connecting to the latest generation Apple BT keyboard ( the one with the
USB port & no batteries ) fails on an Ubuntu Touch device, as when you
press the "Connect" button on the device page, a dialog titled
"Bluetooth Pairing Request" is displayed, with the
Re-tested on krillin ( rc-proposed/bq-aquaris.en / 270 ), this time with
bluez 5.37 installed from the silo.
@Simon, how could this not be a system settings app failure? As I
pointed out in my description, pairing this keyboard works fine with
every other device I tried, including two Ubuntu
** Attachment added: "system settings log from krillin"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591779/+files/application-legacy-ubuntu-system-settings-.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858
Title:
[bluetooth]
18 matches
Mail list logo
