Bug 29116

Summary: Mouse buttons stop working although mouse still controls the pointer
Product: Mageia Reporter: w unruh <unruh>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: Normal CC: davidwhodgins, lewyssmith, ouaurelien
Version: 8Keywords: NEEDINFO
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: ?? CVE:
Status comment:

Description w unruh 2021-06-13 02:49:12 CEST
Description of problem:
Since I upgraded to Mga8 I have not twice had the mouse buttons stop working. In one case rebooting would start them working again, but logging out and in would not. The mouse still works in the sense that the mouse pointer would still skitter across the screen when I moved the mouse. But the focus would not follow the mouse. Since this happened on two different machines with different mice, (one was a microsoft usb wireless mouse, and the other was microsoft plugin mouse) I figure it is something that needs to be reported. There was nothing in dmesg to indicate anything. 

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

How reproducible: It has happened on two different machine about a month after I converted to Mga8 and within a week of each other. 



Steps to Reproduce: No idea. It just happened.
Comment 1 Dave Hodgins 2021-06-13 17:38:53 CEST
I've had that on multiple mice in the past, both wired and wireless. The problem
is that the plastic wears out. Temporary solution was to take it apart and put
a layer or two of tape in between the plastic part being pushed on and the
plastic switch is pushes on. Getting the thickness right if a pain and the tape
compresses with use, so it's a temporary solution until the mouse can be
replaced. It seems they were out faster now than they did in the past. Planned
obsolescence perhaps.

Anyway that was a hardware problem, not a software problem. Leaving this open
for a while to see if others reproduce the issue. If not, in a couple of weeks
will close as invalid.

And if it is a software problem, what desktop environment?

CC: (none) => davidwhodgins

Comment 2 w unruh 2021-06-13 20:13:46 CEST
Actually, no. When I rebooted, the mouse worked fine, on at least one of the machines. The other one, I had replaced the mouse  by the time I rebooted, and thus no longer had a problem. 
Ie, at least on the one, a reboot, which would probably not have altered the hardware, fixed the problem. That strongly suggests software, not hardware.
Also none of the buttons worked, not just one stopped, which suggests it is not simply a contact. 
Thirdly I have "focus follows mouse" implemented, and when I moved the mouse pointer over a window, the focus did not shift to that window (no mouse clicks required) . Again, that suggests software. 
In one case it was Plasma, and in the other it was XFCE. 
Had it just been one machine, I would have passed it off as one of those weird glitches which happens with computers, easily fixed, and thus uninteresting. When it was two, it began to look like a pattern. It never happened with Mga7. 
In the latest case, I was at the computer, with two browser windows open (chrome and chromium). I talked to my wife for a minute and when I returned to the computer, the mouse had ceased behaving as described. I unplugged the mouse and replugged it-- no change. I plugged into another usb port, still no change. 
The key board worked, the mouse moved, but no focus and no clicks. dmesg showed the mouse being unplugged and replugged, but no other information. Only reboot solved the problem.
Comment 3 Lewis Smith 2021-06-13 21:27:50 CEST
> Only reboot solved the problem
Did you ever try re-starting X (Ctrl/Alt/Bksp/Bksp) ? Although this is hardly a satisfactory solution - if it works -, it is less drastic than a re-boot.

> I have "focus follows mouse" implemented (no mouse clicks required)
Have you tried disabling this feature to see whether the problem of mouse clicks having no effect still happens ?

CC: (none) => lewyssmith

Comment 4 Aurelien Oudelet 2021-06-28 22:42:08 CEST
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

CC: (none) => ouaurelien
Keywords: (none) => NEEDINFO
Status: NEW => NEEDINFO

Comment 5 w unruh 2021-06-28 23:54:57 CEST
Yes, I believe I tried the alt-ctrl-Bksp twice, but that did not solve the problem.
No I did not change "focus follows mouse" There was no way I could select anything without mouse buttons, and certainly not SettingsManager. (No mue buttons leaves you pretty helpless).
Comment 6 Lewis Smith 2021-06-29 21:19:52 CEST
In the past I once or twice had boots where the [PS/2] mouse was not recognised at all, as if the kernel had not picked it up on starting. An immediate re-boot always brought it back.

> I believe I tried the alt-ctrl-Bksp twice, but that did not solve the problem
Meaning that even after re-starting X from the login screen, the bad mouse behaviour persisted?

> There was no way I could select anything without mouse buttons
One agrees - a clickless mouse is useless.

Can we understand that you still have the problem?
* Does the mouse normally work correctly, clicks included?
* When it does not - how often?
* When it does not, does it start OK then stop working during the session?
* Or is it apparent at startup that it is not working correctly?
> I have "focus follows mouse" implemented
Are you able to disable this feature? And if so, does it change the situation?
Comment 7 w unruh 2021-06-29 23:08:55 CEST
No, I do not still have the problem. On the first machine I disconnected the 
Microsoft wireless keyboard and mouse and replaced them with a plugin keyboard
and mouse, and that seemed to have  solved the problem. That was a suboptimal solution as my 
wife, whose computer that was, really liked the MS keyboard and wireless 
mouse.
I reported it because two days later my own machine-- keyboard and mouse both
plugin, displayed the same symptom-- the mouse stopped working in that the 
buttons refused to work (ie, the computer refused to respond to button clicks)
After trying many things, including alt-ctrl-bksp-bksp, none of which worked,
I rebooted the machine (alt-ctrl-F2, login and run systemctl shutdown, and 
then boot. ) the mouse worked again and has since then. Two different 
machines, both with the same symptoms, with different mice, and both with 
recent upgrade to MGA8, made it seem that there was some problem with Mga8. 
However, the problem has not re-occurred on either machine. However I still refuse to regard it as a co-incidence.
Comment 8 Lewis Smith 2021-06-30 21:19:32 CEST
Notwithstanding, this looks OK to close at least for the moment.
If the problem recurs - not just once, spuriously, but with some repetition - please re-open this bug taking note of the questions in comment 6.
Previously, from within the session where it happens (before rebooting etc), copy the 'X' log for the bad session:
 $ cp /var/log/Xorg.0.log  xlog.txt       [say]
and once you are back up & running, attach the copy to this bug; you can add all other comments at the same time.

Status: NEEDINFO => RESOLVED
Resolution: (none) => WORKSFORME