Description of problem: I have recently started having troubles where the mouse will freeze. I am running plasma on a Dell XPS13 9760 machine ( 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)) It happens seemingly randomly but seems to be correlated with my using Chrome. This has now happened in the last couple of weeks about 3 or 4 times on two machines (updated) running Mageia 7.1 If I wait for minutes it will sometimes clear by itself. Or if I go to a console (alt ctl F2) and then back to X (alt-ctrl-F1) the mouse works again. Sometimes it seems to be a keyboard freeze as well.
> It happens seemingly randomly but seems to be correlated with my using Chrome It would be useful to know if this really *is* related. Can you live with a completely different browser for some time to test this aspect? Are you referring to our 'chromium-browser' or 'chromium-browser-stable'; or something direct from Google? If the last, and you find there is a correlation, you are on your own. Have you noticed this recently after an update to one of these? You can do: $ rpm -qa --last | grep chrome to see the latest update. This might concern the X server, so could be related to a recent update of *that*: $ rpm -qa --last | grep xorg which shows for me early November. Does this correspond? If you have another desktop available (there is usually a simple one), try using that to see whether it still happens; is it desktop related? This is inconvenient, but you can still do all work. You will appreciate that this sort of problem is difficult to pin down.
CC: (none) => lewyssmithSource RPM: ?? => (none)
I am refering to Chrome, not chromium. However, I am not sure at all that the problem is with Chrome. Sometimes chrome is open when this happens, but then that is not unusual (my desktops tend to be messy and chrome is usually open) Ie, it is not at all clear what it is correlated with. The rpoblem happens randomly ab=nd rarely. Sometimes it also seems to be correlated with libreoffice.
It just happened again while I was using Libreoffice. Remembering other times that may well have also been when it occurred then. Again, I did alt-ctrl-F2 and then Alt-ctrl-F1 and things worked again. Anything I can look for next time it occurs?
Actually, I should be more accurate. When I talk about "mouse" I actually mean the trackpad on the XPS13 laptop
Thank you for your extra comments. Let us assume it is not related to any particular application. But I repeat the question about: > recently started having troubles which indicates that this did not happen from installation or upgrade, but perhaps after certain routine updates. $ rpm -qa --last | less will show all packages ordered by their date (most recent first). Can you remember roughly when the problem started, and see what updates there were just before?
Summary: mouse freezes occasionally. => XPS13 laptop trackpad freezes occasionally.
On both machines that have been having this problem I updated about Dec 30 with about 500 packages updated around that time. The first few times I just swore and rebooted regarding them as one-ofs. One I began to realise they were possibly more serious I had forgotten when the problem started. One one of the machines, a desctop with a mouse, the whole system was found frozen this morning, together with a bad router so I coulld not even see if I could login remotely. Sorry, this I know is all useless for debugging the problem, and I guess at best is a very poor data point suggesting that there is something wrong with the X system, and in hope that it will trigger others to report if they notice the same thing. I will try to be more concious about what is going on when these things happen.
> suggesting that there is something wrong with the X system > updated about Dec 30 with about 500 packages To test this, try downgrading X11, any of perhaps these pkgs if they were updated when or since you said: x11-driver-input-* x11-server-common-1.20.5-1.mga7 x11-server-xorg-1.20.5-1.mga7 x11-server-xwayland-1.20.5-1.mga7 [for Gnome] # urpmi --downgrade <pkg> and I suppose you have to be careful not to update it/them along with other things!
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD