Bluetooth bug

Bug #1779413 reported by John Daniels
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Incomplete
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Good afternoon!
I have a small problem. It is connected with the mouse from Microsoft (BTLE Precision Mouse). She does not want to connect on bluetooth. The version of my bluetooth 4.1.
Ubuntu 4.15.0-22.24-generic 4.15.17

```
lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
```

Here's the output when trying to pair:
```
pair E0:52:31:92:AB:5B
Attempting to pair with E0:52:31:92:AB:5B
[CHG] Device E0:52:31:92:AB:5B Connected: yes
[NEW] Primary Service
 /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
 00001801-0000-1000-8000-00805f9b34fb
 Generic Attribute Profile
[NEW] Primary Service
 /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
 0000180a-0000-1000-8000-00805f9b34fb
 Device Information
[NEW] Characteristic
 /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
 00002a29-0000-1000-8000-00805f9b34fb
 Manufacturer Name String
[NEW] Characteristic
 /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
 00002a24-0000-1000-8000-00805f9b34fb
 Model Number String
[NEW] Characteristic
 /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
 00002a26-0000-1000-8000-00805f9b34fb
 Firmware Revision String
[NEW] Characteristic
 /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
 00002a28-0000-1000-8000-00805f9b34fb
 Software Revision String
[NEW] Characteristic
 /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
 00002a50-0000-1000-8000-00805f9b34fb
 PnP ID
[NEW] Characteristic
 /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
 6ff6f99d-536c-4ea6-88a3-c3aabb718b68
 Vendor specific
[CHG] Device E0:52:31:92:AB:5B UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device E0:52:31:92:AB:5B UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device E0:52:31:92:AB:5B UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device E0:52:31:92:AB:5B UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device E0:52:31:92:AB:5B UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device E0:52:31:92:AB:5B UUIDs: 00001813-0000-1000-8000-00805f9b34fb
[CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
[CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
Failed to pair: org.freedesktop.DBus.Error.NoReply
```

journalctl -u bluetooth
```
июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B
июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B
июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B
июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B

```
---
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: pocoz 2614 F...m pulseaudio
 /dev/snd/controlC0: pocoz 2614 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-23 (37 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Timi TM1701
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=21d3a01c-fa57-4a35-8987-095d593fc63f ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-22-generic N/A
 linux-backports-modules-4.15.0-22-generic N/A
 linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/13/2017
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: XMAKB5R0P0502
dmi.board.asset.tag: Any
dmi.board.name: TM1701
dmi.board.vendor: Timi
dmi.board.version: MP
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Timi
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:
dmi.product.family: Timibook
dmi.product.name: TM1701
dmi.sys.vendor: Timi

Revision history for this message
John Daniels (pocoz) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1779413

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
John Daniels (pocoz) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
John Daniels (pocoz) wrote : CRDA.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : CurrentDmesg.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : IwConfig.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : Lspci.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : Lsusb.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : ProcEnviron.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : ProcInterrupts.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : ProcModules.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : PulseList.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : RfKill.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : UdevDb.txt

apport information

Revision history for this message
John Daniels (pocoz) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
John Daniels (pocoz) wrote :

This problem was always. Kernel 4.18 did not solve the problem. Pair does not happen.

tags: added: kernel-bug-exists-upstream
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also, does the mouse never connect at all? Or just not reconnect on login or on resume from suspend?

Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
John Daniels (pocoz) wrote :

The mouse is connected only after its removal and reboot of the bluetooth. But as soon as the mouse turns off falling into a dream, you have to remove it again and restart the bluetooth. Pair does not happen.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, thanks. If it fails after "falling into a dream" then this sounds like bug 1246981, which may be related to the more recent bug 1779289.

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

Other bug subscribers

Remote bug watches

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