Bug 16891 - Erratic mouse click detection in kernel 4.1.8 on Dell desktop computer
Summary: Erratic mouse click detection in kernel 4.1.8 on Dell desktop computer
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-10-04 03:18 CEST by Thomas Andrews
Modified: 2016-11-04 06:18 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Thomas Andrews 2015-10-04 03:18:03 CEST
Description of problem:
After upgrading to kernel 4.1.8, detection of both left and right mouse clicks is erratic in Firefox 41.0.1. Sometimes detection is normal, and other times it takes several tries before the computer responds. Cursor movement and response seem normal at all times. At first I believed that the Adblock Plus add-on could be the source, but reverting to kernel 3.x without changing anything else eliminates the problem.

Hardware involved:
Dell Dimension E310 desktop
Intel P4 64-bit capable processor
2 GB RAM
On-board Intel gpu

This computer is the one that had gpu issues during the testing of kernel 4.1.8. (Bug 16655)

Version-Release number of selected component (if applicable):
Kernel 4.1.8

How reproducible:
Always. At times the problem is bad enough to make Firefox all but unusable.

Steps to Reproduce:
1. Attempt to use the mouse to make selections in Firefox 41.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 William Kenney 2015-10-04 03:32:32 CEST
Wired or wireless mouse/keyboard?

CC: (none) => wilcal.int

Comment 2 Thomas Andrews 2015-10-04 05:06:22 CEST
I knew I was forgetting something. 

Microsoft Wireless USB desktop set:
Microsoft Wireless Optical Mouse 2000 
Microsoft Wireless Multimedia Keyboard 1.1 
Microsoft Wireless Optical Desktop Receiver 2.1 

This desktop set was with the computer when it was given to me in February 2013, and until now has worked flawlessly with Mageia using the universal PS/2 & USB mouse driver.
Comment 3 Thomas Andrews 2015-10-04 05:18:41 CEST
A newly-recharged set of nimh AA batteries in the mouse made no difference.
Comment 4 William Kenney 2015-10-04 05:45:08 CEST
(In reply to Thomas Andrews from comment #2)

> I knew I was forgetting something. 
> 
> Microsoft Wireless USB desktop set:....

Hmmmmm, interesting. FWIW I had to go back to a wired Logitech mouse on
this server as my wireless Logitech mouse started exhibiting exactly
these symptoms. I thought it was the mouse. I changed the battery to
make sure it wasn't that. Hard wired mouse works just fine.
Comment 5 Thomas Andrews 2015-10-04 14:55:17 CEST
(In reply to William Kenney from comment #4)
> 
> Hmmmmm, interesting. FWIW I had to go back to a wired Logitech mouse on
> this server as my wireless Logitech mouse started exhibiting exactly
> these symptoms. I thought it was the mouse. I changed the battery to
> make sure it wasn't that. Hard wired mouse works just fine.

My Logitech wireless keyboard/mouse set (MK320, with the unifying receiver) is working just fine on this computer. This one is AMD-based, using the server kernel, and a nvidia Geforce 6200 video card, so very different hardware from the one with the problem.
Comment 6 Marja Van Waes 2016-11-03 14:33:10 CET
@ Thomas,

Do you still have the hardware with that problem?

If so: is this bug still valid in fully updated Mga5 and/or cauldron?

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Assignee: bugsquad => kernel

Comment 7 Thomas Andrews 2016-11-03 21:20:51 CET
I still have the hardware, but the bug disappeared some time ago. Not sure when now. It may have been when I stopped using Mozilla's bleeding-edge Firefox and went with the version supplied with Mageia. As I recall, I had other problems with Firefox 41. Or, it could have disappeared with a new kernel.

I just don't remember.
Comment 8 Thierry Vignaud 2016-11-04 06:18:09 CET
Closing as old then

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.