2023-12-19 17:37:58

by Brian J. Murrell

[permalink] [raw]
Subject: chrome passkey communication timing out

I am trying to utilize the facility in Chrome to be able to use
passkeys stored on an Android phone with the demo site at passkeys.io.

I have tried this on 3 computers I have access to and it only seems to
work on one of them and the Bluetooth operation fails on two of them.

The one that works is running Fedora 38 with bluez-5.70-5.fc38.x86_64
on a:

Bus 001 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth

BT adapter.

One that is not working is running Fedora 39 with bluez-5.71-
1.fc39.x86_64 on a:

Bus 003 Device 004: ID 0a5c:2121 Broadcom Corp. BCM2210 Bluetooth

BT adapter.

The other one that is not working is also Fedora 39 with bluez-5.71-
1.fc39.x86_64 but I cannot seem to see a BT adapter in the output of
either lspci or lsusb. But I can see that it has a BT adapter:

$ bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# hci0 new_settings: powered bondable ssp br/edr
[bluetooth]# Agent registered
[bluetooth]# [CHG] Controller 70:F3:95:3E:92:34 Pairable: yes

Any clues or hints on how to further debug why these two non-working
systems are non-working given that this does work on the third system?

Cheers,
b.



2023-12-19 17:55:41

by Luiz Augusto von Dentz

[permalink] [raw]
Subject: Re: chrome passkey communication timing out

Hi Brian,

On Tue, Dec 19, 2023 at 12:35 PM Brian J. Murrell <[email protected]> wrote:
>
> I am trying to utilize the facility in Chrome to be able to use
> passkeys stored on an Android phone with the demo site at passkeys.io.
>
> I have tried this on 3 computers I have access to and it only seems to
> work on one of them and the Bluetooth operation fails on two of them.
>
> The one that works is running Fedora 38 with bluez-5.70-5.fc38.x86_64
> on a:
>
> Bus 001 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth
>
> BT adapter.
>
> One that is not working is running Fedora 39 with bluez-5.71-
> 1.fc39.x86_64 on a:
>
> Bus 003 Device 004: ID 0a5c:2121 Broadcom Corp. BCM2210 Bluetooth
>
> BT adapter.
>
> The other one that is not working is also Fedora 39 with bluez-5.71-
> 1.fc39.x86_64 but I cannot seem to see a BT adapter in the output of
> either lspci or lsusb. But I can see that it has a BT adapter:
>
> $ bluetoothctl
> Waiting to connect to bluetoothd...[bluetooth]# hci0 new_settings: powered bondable ssp br/edr
> [bluetooth]# Agent registered
> [bluetooth]# [CHG] Controller 70:F3:95:3E:92:34 Pairable: yes
>
> Any clues or hints on how to further debug why these two non-working
> systems are non-working given that this does work on the third system?

Check with btmon what if that is generating any traffic.

> Cheers,
> b.
>
>


--
Luiz Augusto von Dentz

2023-12-21 14:27:04

by Brian J. Murrell

[permalink] [raw]
Subject: Re: chrome passkey communication timing out

On Tue, 2023-12-19 at 12:49 -0500, Luiz Augusto von Dentz wrote:
> Hi Brian,

Hi Luiz.

> Check with btmon what if that is generating any traffic.

Ah, yes. btmon. Forgot all about that.

Bluetooth monitor ver 5.71
= Note: Linux version 6.5.11-300.fc39.x86_64 (x86_64) 0.208407
= Note: Bluetooth subsystem version 2.22 0.208411
= New Index: 70:F3:95:3E:92:34 (Primary,USB,hci0) [hci0] 0.208412
= Open Index: 70:F3:95:3E:92:34 [hci0] 0.208413
= Index Info: 70:F3:95:3E:92:34 (Broadcom Corporation) [hci0] 0.208414
@ MGMT Open: bluetoothd (privileged) version 1.22 {0x0001} 0.208415
@ MGMT Command: Start Service Discovery (0x003a) plen 4 {0x0001} [hci0] 24.471901
Address type: 0x06
LE Public
LE Random
RSSI: invalid (0x7f)
UUIDs: 0
@ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 24.471919
Start Service Discovery (0x003a) plen 1
Status: Not Supported (0x0c)
Address type: 0x06
LE Public
LE Rando
The "Not Supported" is not entirely lost on me. But what exactly is
not supported?

Cheers,
b.


2023-12-21 15:29:01

by Luiz Augusto von Dentz

[permalink] [raw]
Subject: Re: chrome passkey communication timing out

Hi Brian,

On Thu, Dec 21, 2023 at 9:27 AM Brian J. Murrell <[email protected]> wrote:
>
> On Tue, 2023-12-19 at 12:49 -0500, Luiz Augusto von Dentz wrote:
> > Hi Brian,
>
> Hi Luiz.
>
> > Check with btmon what if that is generating any traffic.
>
> Ah, yes. btmon. Forgot all about that.
>
> Bluetooth monitor ver 5.71
> = Note: Linux version 6.5.11-300.fc39.x86_64 (x86_64) 0.208407
> = Note: Bluetooth subsystem version 2.22 0.208411
> = New Index: 70:F3:95:3E:92:34 (Primary,USB,hci0) [hci0] 0.208412
> = Open Index: 70:F3:95:3E:92:34 [hci0] 0.208413
> = Index Info: 70:F3:95:3E:92:34 (Broadcom Corporation) [hci0] 0.208414
> @ MGMT Open: bluetoothd (privileged) version 1.22 {0x0001} 0.208415
> @ MGMT Command: Start Service Discovery (0x003a) plen 4 {0x0001} [hci0] 24.471901
> Address type: 0x06
> LE Public
> LE Random
> RSSI: invalid (0x7f)
> UUIDs: 0
> @ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 24.471919
> Start Service Discovery (0x003a) plen 1
> Status: Not Supported (0x0c)
> Address type: 0x06
> LE Public
> LE Rando
> The "Not Supported" is not entirely lost on me. But what exactly is
> not supported?

I think it doesn't support LE thus why it can't discover.

> Cheers,
> b.
>
>


--
Luiz Augusto von Dentz

2023-12-21 16:02:06

by Brian J. Murrell

[permalink] [raw]
Subject: Re: chrome passkey communication timing out

On Thu, 2023-12-21 at 10:27 -0500, Luiz Augusto von Dentz wrote:
> Hi Brian,

Hi again Luiz.

> I think it doesn't support LE thus why it can't discover.

Damn. I was wondering if BLE was the problem. That means needing to
replace or add dongles to some older machines. :-(

But this is where it generally sucks. Trying to figure out which
"brand/model"s of BT adapters out there available to purchase that are
actually supported by Bluez. Is there any guidance available on how to
successfully do this, other than the trial-and-error of buying and
(hopefully) returning products until one finds one that works?

Cheers,
b.


2023-12-22 17:05:26

by Brian J. Murrell

[permalink] [raw]
Subject: Re: chrome passkey communication timing out

On Thu, 2023-12-21 at 10:27 -0500, Luiz Augusto von Dentz wrote:
> Hi Brian,

Hi Luiz,


> I think it doesn't support LE thus why it can't discover.

I got a new BT adapter. btmon looks better, but still does not
complete and times out:

Bluetooth monitor ver 5.71
btmon[2006905]: = Note: Linux version 6.6.4-200.fc39.x86_64 (x86_64) 0.899623
btmon[2006905]: = Note: Bluetooth subsystem version 2.22 0.899626
= New Index: 8C:88:2B:45:A0:8A (Primary,USB,hci0) [hci0] 0.899627
= Open Index: 8C:88:2B:45:A0:8A [hci0] 0.899628
= Index Info: 8C:88:2B:45:A0:8A (Realtek Semiconductor Corporation) [hci0] 0.899628
bluetoothctl[2000095]: @ MGMT Open: bluetoothctl version 1.22 {0x0002} 0.899629
bluetoothd[1033357]: @ MGMT Open: bluetoothd (privileged) version 1.22 {0x0001} 0.899630
bluetoothd[1033357]: @ MGMT Command: Stop Discovery (0x0024) plen 1 {0x0001} [hci0] 4.618617
Address type: 0x07
BR/EDR
LE Public
LE Random
< HCI Command: Inquiry Cancel (0x01|0x0002) plen 0 #1 [hci0] 4.618650
> HCI Event: Command Complete (0x0e) plen 4 #2 [hci0] 4.715392
Inquiry Cancel (0x01|0x0002) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 #3 [hci0] 4.715514
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 4.716388
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 4.716427
Stop Discovery (0x0024) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 4.716432
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
bluetoothd[1033357]: @ MGMT Command: Start Service Discovery (0x003a) plen 4 {0x0001} [hci0] 4.716731
Address type: 0x07
BR/EDR
LE Public
LE Random
RSSI: invalid (0x7f)
UUIDs: 0
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 13 #5 [hci0] 4.716756
Own address type: Random (0x01)
Filter policy: Accept all advertisement (0x00)
PHYs: 0x05
Entry 0: LE 1M
Type: Active (0x01)
Interval: 22.500 msec (0x0024)
Window: 11.250 msec (0x0012)
Entry 1: LE Coded
Type: Active (0x01)
Interval: 22.500 msec (0x0024)
Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4 #6 [hci0] 4.717373
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 #7 [hci0] 4.717403
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4 #8 [hci0] 4.718370
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: Inquiry (0x01|0x0001) plen 5 #9 [hci0] 4.718401
Access code: 0x9e8b33 (General Inquiry)
Length: 10.24s (0x08)
Num responses: 0
> HCI Event: Command Status (0x0f) plen 4 #10 [hci0] 4.719366
Inquiry (0x01|0x0001) ncmd 2
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 4.719388
Start Service Discovery (0x003a) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 4.719394
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Enabled (0x01)
> HCI Event: Inquiry Complete (0x01) plen 1 #11 [hci0] 15.038405
Status: Success (0x00)
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 15.067415
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 #12 [hci0] 15.067466
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
bluetoothd[1033357]: @ MGMT Command: Start Service Discovery (0x003a) plen 4 {0x0001} [hci0] 15.068155
Address type: 0x07
BR/EDR
LE Public
LE Random
RSSI: invalid (0x7f)
UUIDs: 0
> HCI Event: Command Complete (0x0e) plen 4 #13 [hci0] 15.068377
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 13 #14 [hci0] 15.068403
Own address type: Random (0x01)
Filter policy: Accept all advertisement (0x00)
PHYs: 0x05
Entry 0: LE 1M
Type: Active (0x01)
Interval: 22.500 msec (0x0024)
Window: 11.250 msec (0x0012)
Entry 1: LE Coded
Type: Active (0x01)
Interval: 22.500 msec (0x0024)
Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4 #15 [hci0] 15.069393
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 #16 [hci0] 15.069426
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4 #17 [hci0] 15.070419
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: Inquiry (0x01|0x0001) plen 5 #18 [hci0] 15.070465
Access code: 0x9e8b33 (General Inquiry)
Length: 10.24s (0x08)
Num responses: 0
> HCI Event: Command Status (0x0f) plen 4 #19 [hci0] 15.071383
Inquiry (0x01|0x0001) ncmd 2
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 15.071425
Start Service Discovery (0x003a) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 15.071552
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Enabled (0x01)
> HCI Event: Inquiry Complete (0x01) plen 1 #20 [hci0] 25.388387
Status: Success (0x00)
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 25.819382
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 #21 [hci0] 25.819409
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
bluetoothd[1033357]: @ MGMT Command: Start Service Discovery (0x003a) plen 4 {0x0001} [hci0] 25.819549
Address type: 0x07
BR/EDR
LE Public
LE Random
RSSI: invalid (0x7f)
UUIDs: 0
> HCI Event: Command Complete (0x0e) plen 4 #22 [hci0] 25.820386
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 13 #23 [hci0] 25.820435
Own address type: Random (0x01)
Filter policy: Accept all advertisement (0x00)
PHYs: 0x05
Entry 0: LE 1M
Type: Active (0x01)
Interval: 22.500 msec (0x0024)
Window: 11.250 msec (0x0012)
Entry 1: LE Coded
Type: Active (0x01)
Interval: 22.500 msec (0x0024)
Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4 #24 [hci0] 25.821400
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 #25 [hci0] 25.821454
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4 #26 [hci0] 25.822377
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: Inquiry (0x01|0x0001) plen 5 #27 [hci0] 25.822397
Access code: 0x9e8b33 (General Inquiry)
Length: 10.24s (0x08)
Num responses: 0
> HCI Event: Command Status (0x0f) plen 4 #28 [hci0] 25.823387
Inquiry (0x01|0x0001) ncmd 2
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 25.823448
Start Service Discovery (0x003a) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 25.823454
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Enabled (0x01)
> HCI Event: Inquiry Result (0x02) plen 15 #29 [hci0] 28.402386
Num responses: 1
Address: 64:A2:F9:1B:1A:C9 (OnePlus Technology (Shenzhen) Co., Ltd)
Page scan repetition mode: R1 (0x01)
Page period mode: P2 (0x02)
Page scan mode: Mandatory (0x00)
Class: 0x5a020c
Major class: Phone (cellular, cordless, payphone, modem)
Minor class: Smart phone
Networking (LAN, Ad hoc)
Capturing (Scanner, Microphone)
Object Transfer (v-Inbox, v-Folder)
Telephony (Cordless telephony, Modem, Headset)
Clock offset: 0x00c8
@ MGMT Event: Device Found (0x0012) plen 19 {0x0001} [hci0] 28.402413
BR/EDR Address: 64:A2:F9:1B:1A:C9 (OnePlus Technology (Shenzhen) Co., Ltd)
RSSI: invalid (0x7f)
Flags: 0x00000003
Confirm Name
Legacy Pairing
Data length: 5
Class: 0x5a020c
Major class: Phone (cellular, cordless, payphone, modem)
Minor class: Smart phone
Networking (LAN, Ad hoc)
Capturing (Scanner, Microphone)
Object Transfer (v-Inbox, v-Folder)
Telephony (Cordless telephony, Modem, Headset)
> HCI Event: Inquiry Complete (0x01) plen 1 #30 [hci0] 36.139386
Status: Success (0x00)
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 36.571404
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 #31 [hci0] 36.571427
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
bluetoothd[1033357]: @ MGMT Command: Start Service Discovery (0x003a) plen 4 {0x0001} [hci0] 36.571564
Address type: 0x07
BR/EDR
LE Public
LE Random
RSSI: invalid (0x7f)
UUIDs: 0
> HCI Event: Command Complete (0x0e) plen 4 #32 [hci0] 36.572414
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 13 #33 [hci0] 36.572446
Own address type: Random (0x01)
Filter policy: Accept all advertisement (0x00)
PHYs: 0x05
Entry 0: LE 1M
Type: Active (0x01)
Interval: 22.500 msec (0x0024)
Window: 11.250 msec (0x0012)
Entry 1: LE Coded
Type: Active (0x01)
Interval: 22.500 msec (0x0024)
Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4 #34 [hci0] 36.573388
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 #35 [hci0] 36.573825
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4 #36 [hci0] 36.575399
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: Inquiry (0x01|0x0001) plen 5 #37 [hci0] 36.575432
Access code: 0x9e8b33 (General Inquiry)
Length: 10.24s (0x08)
Num responses: 0
> HCI Event: Command Status (0x0f) plen 4 #38 [hci0] 36.576386
Inquiry (0x01|0x0001) ncmd 2
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 36.576411
Start Service Discovery (0x003a) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 36.576417
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Enabled (0x01)
> HCI Event: Inquiry Result (0x02) plen 15 #39 [hci0] 38.867399
Num responses: 1
Address: 64:A2:F9:1B:1A:C9 (OnePlus Technology (Shenzhen) Co., Ltd)
Page scan repetition mode: R1 (0x01)
Page period mode: P2 (0x02)
Page scan mode: Mandatory (0x00)
Class: 0x5a020c
Major class: Phone (cellular, cordless, payphone, modem)
Minor class: Smart phone
Networking (LAN, Ad hoc)
Capturing (Scanner, Microphone)
Object Transfer (v-Inbox, v-Folder)
Telephony (Cordless telephony, Modem, Headset)
Clock offset: 0x00c8
@ MGMT Event: Device Found (0x0012) plen 19 {0x0001} [hci0] 38.867459
BR/EDR Address: 64:A2:F9:1B:1A:C9 (OnePlus Technology (Shenzhen) Co., Ltd)
RSSI: invalid (0x7f)
Flags: 0x00000003
Confirm Name
Legacy Pairing
Data length: 5
Class: 0x5a020c
Major class: Phone (cellular, cordless, payphone, modem)
Minor class: Smart phone
Networking (LAN, Ad hoc)
Capturing (Scanner, Microphone)
Object Transfer (v-Inbox, v-Folder)
Telephony (Cordless telephony, Modem, Headset)
bluetoothd[1033357]: < ACL Data TX: Handle 5 flags 0x00 dlen 7 #40 [hci0] 41.530706
Channel: 69 len 3 [PSM 0 mode Basic (0x00)] {chan 65535}
a2 04 03 ...
> HCI Event: Number of Completed Packets (0x13) plen 5 #41 [hci0] 41.631433
Num handles: 1
Handle: 5
Count: 1
bluetoothd[1033357]: < ACL Data TX: Handle 5 flags 0x00 dlen 7 #42 [hci0] 41.824387
Channel: 69 len 3 [PSM 0 mode Basic (0x00)] {chan 65535}
a2 04 01 ...
> HCI Event: Number of Completed Packets (0x13) plen 5 #43 [hci0] 41.830391
Num handles: 1
Handle: 5
Count: 1

Anything useful in that output?

Cheers,
b.


Attachments:
signature.asc (499.00 B)
This is a digitally signed message part

2023-12-26 17:06:24

by Brian J. Murrell

[permalink] [raw]
Subject: Re: chrome passkey communication timing out

On Fri, 2023-12-22 at 12:05 -0500, Brian J. Murrell wrote:
>
> I got a new BT adapter.  btmon looks better, but still does not
> complete and times out:

Seems to be working now. Yay.

Although this morning I had to unplug/replug the USB adapter as my
mouse was not being seen as connected. The journal had such messages
in it:

Dec 26 09:26:44 pc.interlinx.bc.ca bluetoothd[3754244]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info
Dec 26 09:26:50 pc.interlinx.bc.ca bluetoothd[3754244]: profiles/input/device.c:control_connect_cb() connect to 34:88:5D:56:A8:C1: Host is down (112)
Dec 26 09:27:42 pc.interlinx.bc.ca bluetoothd[3754244]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info
Dec 26 09:27:47 pc.interlinx.bc.ca bluetoothd[3754244]: profiles/input/device.c:control_connect_cb() connect to 34:88:5D:56:A8:C1: Host is down (112)

I'll start a new thread if it repeats this behaviour.

Cheers,
b.


Attachments:
signature.asc (499.00 B)
This is a digitally signed message part