Unduping to track the lack of the PIn prompt specific to this bug
** This bug is no longer a duplicate of bug 1576986
UT does not discover bluetooth smart (BLE) devices
** Summary changed:
- Can't connect Logitech Living Room Keyboard [LE]
+ Can't connect Logitech K830 - no PIN prompt [LE]
-
*** This bug is a duplicate of bug 1576986 ***
https://bugs.launchpad.net/bugs/1576986
** This bug has been marked a duplicate of bug 1576986
UT does not discover bluetooth smart (BLE) devices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
@Pat: One important thing: Don't use hciconfig up anymore. Even if
its still there and works to some degree that will only initialize the
controller partly as its using an old kernel API. Use bluetoothctl only
to power on/off bluetooth:
$ bluetoothctl
[bluetooth]# power on
Changing power on succe
phablet@ubuntu-phablet:~$ hciconfig -a
hci0: Type: BR/EDR Bus: UART
BD Address: 38:BC:1A:18:B5:CD ACL MTU: 1021:8 SCO MTU: 244:4
DOWN
RX bytes:778 acl:0 sco:0 events:52 errors:0
TX bytes:3483 acl:0 sco:0 commands:52 errors:0
Features: 0xbf 0x3e 0x8d 0xf
log while trying to pair the mouse
** Attachment added: "syslogwithbtup"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+attachment/4587830/+files/syslogwithbtup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Attachment added: "main.conf"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+attachment/4587828/+files/main.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
Ca
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+attachment/4587829/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
Can't co
Tried the above settings with the test kernel, the indicators and settings tell
me bt is off.
Note that the echo did not take effect and I manually edited the main.conf file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15319
@Pat: Did you saved any logs from that attempt?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
Can't connect Logitech Living Room Keyboard [LE]
To manage notifications about this bug
I tried the instructions in comment #9 with a smart mouse, the mouse was
not visible in the UI, and I could not pair it (authentication failed)
in bluetoothctl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Ok, there seems to be another problem I didn't respected yet. Powering a
controller with hciconfig will bring it into a state where not all
subsystems are initialized required for LE support. We still have a udev
rule in our bluez package included which will try to power a bluetooth
controller via
I went again through the logs and came across the following:
[ 1044.196326] Bluetooth: SMP security requested but not available
which is then followed by a lot messages like:
Jan 20 08:53:28 samsung930X3G bluetoothd[3988]: Report Map read failed:
Attribute requires authentication before read/
Added a task for ubuntu-system-settings as LE devices aren't considered
at all by Bluetooth settings.
** Description changed:
Cannot connect a Logitech Illuminated Living Room keyboard to a device
running bluez5. There are two versions of the keyboard, a unifying
receiver version, and a Bl
** Description changed:
- Trying to pair this device and bluetoothd crashed on my Wily laptop and
- the N4 running latest proposed
+ Cannot connect a Logitech Illuminated Living Room keyboard to a device
+ running bluez5. There are two versions of the keyboard, a unifying
+ receiver version, and
** Summary changed:
- bluetoothd crash with BTLE keyboard
+ Can't connect Logitech Living Room Keyboard [LE]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
Can't connect Logitech Livi
17 matches
Mail list logo