Bug 26206

Summary: After login (via SDDM) after display has been awoken from sleep the mouse is unresposive.
Product: Mageia Reporter: Stephen Usher <steve>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal    
Version: 7   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: x11-server-1.20.5-1.mga7.src.rpm CVE:
Status comment:
Attachments: Xorg.0.log.old

Description Stephen Usher 2020-02-17 13:19:50 CET
Description of problem:

Often after awakening the display when at the login screen (SDDM) and logging in the mouse becomes unresponsive.

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

1.20.5-1.mga7

How reproducible:

Intermittent.

Steps to Reproduce:
1. Log out.
2. Let the display go to sleep
3. Log in
Comment 1 Stephen Usher 2020-02-17 13:20:47 CET
Created attachment 11510 [details]
Xorg.0.log.old
Comment 2 Lewis Smith 2020-02-19 11:40:06 CET
Thank you for the log.
Again, can you say whether this problem arose from a new installation, or after an upgrade.
Does it happen:
- even at the first login, if you let the login screen go blank first?
- or only after logout/let login screen go blank/login?
Can you recover by re-starting X (unobtrusive at the login stage) by:
 Ctrl/Alt/Backspace/Backspace

Can you describe your system a little. What keyboard & mouse connections? The log mentions both "USB Optical Mouse" and "PS/2 Generic Mouse". It also shows a lot of ambiguity re keyboard & mouse.

Trying the manoeuvre you describe, on my own system (dedicated K/B and PS/2 connections) with SDDM, the Xorg log is much simpler re logout-await blank screen-login:
...
[  3192.119] (II) event0  - AT Translated Set 2 keyboard: device removed
[  3192.128] (II) event11 - ImPS/2 Generic Wheel Mouse: device removed
[  3192.145] (II) AIGLX: Suspending AIGLX clients for VT switch
[  3205.772] (II) Open ACPI successful (/var/run/acpid.socket)
[  3205.772] (II) AIGLX: Resuming AIGLX clients after VT switch
...
[  3205.839] (II) event0  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[  3205.839] (II) event0  - AT Translated Set 2 keyboard: device is a keyboard
[  3205.848] (II) event11 - ImPS/2 Generic Wheel Mouse: is tagged by udev as: Mouse
[  3205.848] (II) event11 - ImPS/2 Generic Wheel Mouse: device is a pointer

Assigning to tv for X11.

Assignee: bugsquad => thierry.vignaud
Source RPM: x11-xorg-server-1.20.5-1.mga7 (guess) => x11-server-1.20.5-1.mga7.src.rpm

Comment 3 Stephen Usher 2020-02-19 13:27:57 CET
The mouse is a Dell USB mouse. Here is the output from lsusb

% lsusb
Bus 003 Device 003: ID 0430:0005 Sun Microsystems, Inc. Type 6 Keyboard
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 008: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse
Bus 002 Device 009: ID 0424:4060 Standard Microsystems Corp. Ultra Fast Media Reader
Bus 002 Device 007: ID 0424:2640 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 006: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Comment 4 Stephen Usher 2020-02-28 16:11:10 CET
After accidentally turning my monitor off (the mouse is connected via a USB hub in the monitor) and back on again the mouse stopped working on the X server.

So, it looks like this bug is to do with the X server failing to dynamically pick up and configure HID devices.
Comment 5 Aurelien Oudelet 2021-07-06 13:15:31 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 6 Marja Van Waes 2021-09-07 14:09:41 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Resolution: (none) => OLD
Status: NEW => RESOLVED