SUMMARY *** I have my laptop set to ONLY turn off the screen when the lid is closed, no hibernate, sleep, logout etc is enabled When i close the lid the screen shuts off as expected and everything stays running as expected and desired When i open the lid the display does not turn on until i press a key, it should turn on as soon as the lid is opened *** STEPS TO REPRODUCE 1. In system settings, select power management and under "Button handling events" select to "Turn of Screen" when lid is closed, make sure there is no hibernate, sleep etc selected anywhere on the page, click apply and close system settings 2. close laptop lid, the screen will go black as expected and desired 3. open the lid and the screen stays turned off until you press a key or move the mouse OBSERVED RESULT the screen stays turned off until you press a key or move the mouse EXPECTED RESULT The screen should re-enable and return to normal state SOFTWARE/OS VERSIONS KDE 5.103.0 Plasma 5.27.1 Qt: 5.15.8 Kernel: 6.1.12-1-default x86_64 Xorg 21.1.7 (I am not using wayland) Not using an external display OS: openSUSE Tumbleweed 2023-02-25 Manufacturer: ASUSTeK COMPUTER INC. Product Name: ZenBook UX535LI_UX535LI lshw shows: *-input:1 product: Lid Switch physical id: 2 logical name: input1 logical name: /dev/input/event1 capabilities: platform ADDITIONAL INFORMATION I have no idea what module is involved hence the selection of powerdevil, please change that if appropriate How can i provide more info? I remember there is a program that dumps out kde state and info but the name eludes me.
In general, when the screen is turned off, user interaction is required to turn it back on. Perhaps the issue here is that opening the lid isn't counted as user interaction.
ok, so then how do i make opening the lid a user interaction? This (opening the lid and having the display turn on) is not new behavior, it has always worked on earlier versions of KDE. I can't say exactly when this stopped working but I'm guessing within the last year or so. How can i provide more information to diagnose this?
It's just a bug; a developer will need to change the code to fix it.