Bug 390977

Summary:	Turning off display with xset results in screenlocker freezing when display is turned on again
Product:	[Unmaintained] kscreenlocker	Reporter:	Kishore Gopalakrishnan <kishore96>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bshah, mgraesslin
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Kishore Gopalakrishnan 2018-02-24 01:45:16 UTC

Version: 5.12.2 (could not find relevant option in dropdown)

Steps to reproduce:
1. Set the command 'xset dpms force off' to be run on screen locking.
2. Lock the screen
3. Move the mouse to activate the display again.
4. Switch to a tty and switch back the the graphical display.

Observed results:
After step 3, we find that the screenlocker does not update the display (for eg., does not display stars or cursor when typing password). However, the mouse cursor is movable. After switching to a tty and back, the screenlocker behaves normally. If we type something after step 3, and then perform step 4, we see that stars are shown in the input box. One can also 'unlock' the screen by typing the password and pressing enter. However, the display does not update until we switch to a tty and back.

Expected result:
The screenlocker should update the display accroding to input after the display is turned off and on again using xset.


I am using Intel integrated graphics, on Arch Linux. Downgrading the kscreenlocker package to 5.11.5 fixes the issue.

Comment 1 Kishore Gopalakrishnan 2018-02-24 01:49:48 UTC

Correction: In the steps to reproduce, the command to run should probably be '/usr/bin/sleep 1.0 && /usr/bin/xset dpms force off'. Alternatively, one could have a terminal window open with 'sleep 10 && xset dpms force off' running before locking the screen.

Comment 2 Kishore Gopalakrishnan 2018-03-07 08:08:12 UTC

I cannot reproduce this with kscreenlocker 5.12.3.

Comment 3 Christoph Feck 2018-08-03 09:21:41 UTC

Thanks for the update; changing status.

I only tested it using "sleep 2 ; xset dpms force suspend" in the executed script, but I didn't see any freezing either.