Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44823 - [linux] LID0 always reports closed after first close
Attached to Project:
Arch Linux
Opened by Rodrigo Toste Gomes (rgomes) - Sunday, 03 May 2015, 06:35 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 15 October 2017, 14:16 GMT
Opened by Rodrigo Toste Gomes (rgomes) - Sunday, 03 May 2015, 06:35 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 15 October 2017, 14:16 GMT
|
DetailsDescription:
The state of the LID0 device is always "closed" after I close it for the first time. If I boot it up, it is in the correct state ("open"), but after I close it, it gets stuck in that state. This is a hurdle, because it makes it impossible to use the lid to suspend, since systemd will just keep suspending if I open it. Opening the LID does wake the computer up, and turns on backlight (closing it turns them off). Additional info: This bug has been present for over a year, and it happens with the Razer Blade laptops (other people have confirmed this, and I own two of them, and both have this issue - it is reproducible in other distros). Steps to reproduce: Close LID, and reopen. |
This task depends upon
Is this issue solved for you?