FS#68382 - [Gnome-shell] Mouse is not working after unlocking gdm

Attached to Project: Arch Linux
Opened by Nicolas Repentin (ouafnico) - Thursday, 22 October 2020, 14:52 GMT
Last edited by Toolybird (Toolybird) - Friday, 02 June 2023, 07:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Using Gnome 3.38, after unlocking my session, I can't use any mouse (or trackpad) unless I close and reopen my session.
The mouse is moving, but the left clic isn't working, and the right clic is, only on some windows (contextual menu on title bar).

I don't known if it's a gnome bug, or a libinput bug. I will try to rollback some packages to test.
I don't have anything usefull on journalctl, except a lot of messages like:
gnome-shell[28829]: libinput error: event5 - Dell KB216 Wired Keyboard: client bug: event processing lagging behind by 18ms, your system is too slo

(or the same for my mouse)

If you got ideas, I can test anything or provide specifics logs/results of commands.


Additional info:
* Gnome 3.38.1
* libinput 1.16.2-1
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 02 June 2023, 07:03 GMT
Reason for closing:  No response
Additional comments about closing:  Plus it's old and stale. If still an issue, please report upstream.
Comment by Nicolas Repentin (ouafnico) - Thursday, 22 October 2020, 15:19 GMT
After (a lot) of tests.
I'm using a lenovo T490 with a lenovo dock USB-C.
The laptop is always closed, and I'm using 2 screens on the dock.

After a suspend, when the system wakes up, I unlock the gdm and I got the bug.
If it's a simple lock (no suspend), I don't have the bug.

When I got the bug, if I open the laptop, just enough to the screen to power up, and close it, the bug disapear.

Problem somewhere with the detecting of screens?
Comment by mattia (nTia89) - Saturday, 12 March 2022, 09:06 GMT
I cannot reproduce the bug. Does recent version fixed your issue?

Loading...