Bug 522152

Summary:	Bluetooth mouse gets stuck at regular intervals
Product:	[Fedora] Fedora	Reporter:	Pramod Dematagoda <pmd.lotr.gandalf>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	bnocera, dwmw2, itamar, kernel-maint, marcel, nathaniel, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-17 17:06:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pramod Dematagoda 2009-09-09 15:28:32 UTC

Description of problem: When a bluetooth mouse is used, the mouse pointer keeps freezing at regular intervals, probably because of a lack of input events at that time. I tried my laptop touchpad and a USB mouse and they both work flawlessly.


How reproducible: Configure a bluetooth mouse as an input device through gnome-bluetooth and move it around.


Steps to Reproduce:
1. Press the Bluetooth icon in the notification area and set up a new device.
2. Select the bluetooth mouse from the list.
3. Move it around.
  
Actual results: The mouse pointer keeps freezing at regular intervals for about 1 second and then keeps going like nothing happened.


Expected results: The mouse pointer should keep moving fluidly without interruption.


Additional info: The events seem to be coming in late at that time since if I right click the mouse the event does work after the mouse pointer gets unfrozen, but I cannot be sure since I did this manually, so I may just be slow. :)

Comment 1 Bastien Nocera 2009-09-09 17:29:03 UTC

Input devices are handled in the kernel.

Comment 2 Nathaniel McCallum 2009-09-17 16:13:31 UTC

This bug is a duplicate of 516756.

Comment 3 Bastien Nocera 2009-09-17 17:06:06 UTC


*** This bug has been marked as a duplicate of bug 516756 ***