kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #60353
[Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.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'.
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.15-rc5-utopic/
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318639
Title:
Bluetooth mouse connects but does not move pointer
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Ubuntu 14.04. Bluetooth add new device wizard finished without any
error. Bluetooth applet shows Bluetooth enabled. The applet shows that
the mouse is connected too, if user (me) click it once. It can auto-
reconnect this way on reboot. Whenever it is 'connected', power applet
can show the batter remains for the mouse - and when the mouse's
batter depletes, the power applet knows it and report correctly.
The problem: cursor doesn't move. In fact, if I boot into Windows 8.0
on the same host, the cursor moves. The same mouse works fine on
Windows XP too.It doesn't have on/off switch.
dmesg:
Code:
[ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 129.914256] Bluetooth: HIDP socket layer initialized
[ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0
[ 129.953134] input: Bluetooth Mouse as /devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14
[ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72
The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to):
Code:
$ ls /devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14
ls: no se puede acceder a /devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio
XINPUT has:
Code:
$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ eGalax Inc. USB TouchController id=9 [slave pointer (2)]
⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)]
⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)]
⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)]
↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)]
↳ USB 2.0 Camera id=14 [slave keyboard (3)]
↳ Asus Laptop extra buttons id=15 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)]
Attempt to enable device id=17 has no effect. I am afraid it is always enabled:
Code:
$ xinput --enable 17
It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that:
1. computer boots, /dev/inputs/mouse3 device does not exist
2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth
3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2
Code:
$ ls
by-id event1 event12 event4 event7 js0 mouse1
by-path event10 event2 event5 event8 mice mouse2
event0 event11 event3 event6 event9 mouse0
$ ls
by-id event1 event12 event3 event6 event9 mouse0 mouse3
by-path event10 event13 event4 event7 js0 mouse1
event0 event11 event2 event5 event8 mice mouse2
$ sudo -i
# od < /dev/input/mouse3
^C
# od < /dev/input/mouse2
0000000 177430 034000 177777 174070 034377 177364 171070 034375
0000020 177766 171070 034375 176765 173070 034373 176367 174470
0000040 034374 175367 175070 034373 175775 176470 034375 177375
0000060 177470 034377 177777 177470 014377 000377 176470 014377
0000100 000771 172430 014001 000764 172030 014002 000766 173030
0000120 014001 001371 175030 014001 000775 177030 014001 000377
^C
The most singular thing that happened is: in one occassion, I boot
into Windows 8 and use the mouse, when I reboot back, the cursor go on
moving for a few minutes and mute. It seems, using it in Windows
'oils' the mouse. But I couldn't repeatly reproduce this. I am very
certain about this. The cursor doesn't move even right after the first
time add-new-bluetooth device wizard quit successfully, the single one
time it worked, is after Windows 8 oiled it.
On another behavior: power applet seems to prevent the mouse going
sleep, which it does by itself in a few minutes in Windows - until all
power drains out from the mouse, but it is a trivial problem that I
can afford not to solve.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: tristan 1803 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-28 (13 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: TUL M11JB
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=726d8633-5380-4593-985e-27959193de0e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/01/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Lucid-TUL-0135
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M11JB
dmi.board.vendor: TUL
dmi.board.version: R2.0/R1.1
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 1
dmi.chassis.vendor: TUL
dmi.chassis.version: R2.0/R1.1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrLucid-TUL-0135:bd03/01/2011:svnTUL:pnM11JB:pvrR2.0/R1.1:rvnTUL:rnM11JB:rvrR2.0/R1.1:cvnTUL:ct1:cvrR2.0/R1.1:
dmi.product.name: M11JB
dmi.product.version: R2.0/R1.1
dmi.sys.vendor: TUL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions
References