FS#48713 - [xorg-server] mouse cursor not visible after login, when the computer was on sleep mod or lockscreen
Attached to Project:
Arch Linux
Opened by Thomas Pointhuber (pointhi) - Sunday, 27 March 2016, 17:19 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 28 July 2016, 07:48 GMT
Opened by Thomas Pointhuber (pointhi) - Sunday, 27 March 2016, 17:19 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 28 July 2016, 07:48 GMT
|
Details
Description:
When I close the laptop lid (which cause locking the computer) or I let it go into sleep mode, the mouse cursor is not visible after login. To fix this, I'm currently opening the terminal and executing some gliberish (doesn't have to be a valid bash command), and the mouse curser appears. This bug started to occour a few days ago. Additional info: I'm using an up-to-date Antergos system, with Gnome 3.18 and the Numix-Frost GTK+ theme. The used display manager is lighdm, which displays the cursor correctly in the login screen. Only after the login, the mouse cursor disapears until I enter something into the bash and press enter. Steps to reproduce: Close the laptop lid or send the computer into sleep mode, then you relogin into the system and the mouse cursor is gone. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Thursday, 28 July 2016, 07:48 GMT
Reason for closing: Upstream
Additional comments about closing: we're CC'ed to the upstream bug, Upstream report gives workaround with tty switching or changing over to uxa acceleration.
Thursday, 28 July 2016, 07:48 GMT
Reason for closing: Upstream
Additional comments about closing: we're CC'ed to the upstream bug, Upstream report gives workaround with tty switching or changing over to uxa acceleration.
But I don't know how the internals which are responsible for the curser are working, and if a LightDM greeter is even able to cause such a bug. So I thought it's most likely a bug in the recently updated Arch packages.
downgrading to xorg-server-1.18.1-3-x86_64 (the previous version I found in my pacman cache) solved this issue, and updating it to the current version (xorg-server-1.18.2-4-x86_64) causes the bug to reappear.
Downgrading to xorg-server-1.18.1-3 solves the problem.