Bug 471524 - Automatically turning screen on back again after "xset dpms force off" without any user input
Summary: Automatically turning screen on back again after "xset dpms force off" withou...
Status: RESOLVED DUPLICATE of bug 480026
Alias: None
Product: KScreen
Classification: Plasma
Component: common (other bugs)
Version First Reported In: 5.27.5
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-28 08:08 UTC by ddreamer
Modified: 2025-01-10 17:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Relevent "journalctl" records (30.81 KB, application/octet-stream)
2023-06-28 08:08 UTC, ddreamer 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ddreamer 2023-06-28 08:08:41 UTC 
Created attachment 159947 [details]
Relevent "journalctl" records

SUMMARY

Very self-explanatory in the previous "Summary" Section"

STEPS TO REPRODUCE
1. Under KDE plasma desktop environement, open a terminal, and execute "xset dpms force off"
2. The screen goes blank, followed by showing "no HDMI signal". (Very good till now)
3. After a couple of seconds (about 5-10 sec), without any user input, the screen turns on and show the KDE desktop environment again.

This phenomenon holds even by executing: bash -c "sleep 1; xset dpms force off"

OBSERVED RESULT

Screen re-turning on spontaneously without any user input (both keyboard & mouse)

EXPECTED RESULT

The screen should stay "Turn off" untill user input.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian GNU/Linux 12(Bookworm)
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

I will attach the relevent records from "journalctl" during this event.
Comment 1 ddreamer 2023-06-28 08:12:47 UTC 
Well.... I mean title by previous "Summary" Section"
Comment 2 Zamundaaa 2025-01-10 17:02:15 UTC 

*** This bug has been marked as a duplicate of bug 480026 ***