Ubuntu
linux package

Generic bluetooth mice not recognized

Bug #1747704 reported by Jeb E. on 2018-02-06

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Linux	Unknown	Unknown	linux-kernel-bugs #198697
	linux (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

Generic bluetooth (non-BLE) mice are not being recognized within the Ubuntu System Settings, although these same mice are found, added, installed, and functioning just fine on Windows 10 and Android 7.x+ devices.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-lowlatency 4.13.0.32.34
ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
Uname: Linux 4.13.0-32-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jeb 12678 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 6 10:58:41 2018
HibernationDevice: RESUME=UUID=dc0e59b0-c3f8-4113-9ea4-87b3b2e0c112
MachineType: Dell Inc. Inspiron 13-5368
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-lowlatency root=UUID=b0b38a57-52b5-4e23-be9e-85197724f378 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.13.0-32-lowlatency N/A
linux-backports-modules-4.13.0-32-lowlatency N/A
linux-firmware 1.169.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.name: 01DC01
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd09/14/2017:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn01DC01:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 13-5368
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

Jeb E. (jebeld17) wrote on 2018-02-06:

AlsaInfo.txt Edit (40.6 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (3.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (77.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.7 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (254 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (128.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (442 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.8 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (9.8 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (30.4 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (225.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (191.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2018-02-08:

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.15 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.15

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	New → Incomplete

Revision history for this message

Jeb E. (jebeld17) wrote on 2018-02-09:

I personally do not know. I know that on previous versions of Ubuntu, the mouse worked fine, albeit was on a different PC and different hardware, so I unfortunately cannot say for certain.
If you'd like more debugging info or any more info from me, please let me know, and I will get around to trying your kernel suggestion ASAP.

Thanks,
jeb

tags:

added: kernel-bug

Revision history for this message

Jeb E. (jebeld17) wrote on 2018-02-09:

Latest HardInfo report - February 9th, 2018 Edit (106.9 KiB, text/html)

PS: I unfortunately don't have alot of time today to try this, so I want to make sure I type in the commands and text right if I do go ahead with trying this. I hate to ask, but are you able to help me and show me what I need to type in the Terminal to hop on the latest build and to revert back if necessary?

Thank you :)

Revision history for this message

Jeb E. (jebeld17) wrote on 2018-02-09:

Oh wait, I found the issue.
The mouse was not completely recognized. It was not in pairing mode. (LOL)

Still though, my Settings would show the mouse as an "unknown" device most times even before this thing went into pairing mode, but once I got it in that mode, the computer took a minute and recognized it.

Feature Request/Feedback: Please add a notice to 'gnome-control-center' within "Bluetooth" to place wanted devices into pairing mode, giving a few common examples and methods to activating pairing mode as well.

Thanks!
Jeb

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

linux-kernel-bugs #198697 Edit

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

Ubuntulinux package

Generic bluetooth mice not recognized

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package