Bug 482935 - X11: Weird screen black out when playing media with power saving options
Summary: X11: Weird screen black out when playing media with power saving options
Status: RESOLVED DUPLICATE of bug 482141
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 6.0.1
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2024-03-09 00:18 UTC by Mahbod Karamoozian
Modified: 2024-03-09 21:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mahbod Karamoozian 2024-03-09 00:18:54 UTC
SUMMARY
When you play media generally the idea is that you have no peripheral activity but you don't want the screen to go dark or the computer to suspend due to power saving measures since you want to play the media but something that has regressed in plasma as of plasma 6 is that the power saving process acts a bit weird when you play media but have no peripheral activity (when no media is played or media is paused the behavior is normal)

STEPS TO REPRODUCE
1. Set a screen turn off option in power saving settings to trigger in set time
2. Open a browser instance playing YouTube for example
3. Wait for the set time with no activity but keep the media playing in foreground

OBSERVED RESULT
Screen blacks out with cursor still visible and brightness unmodified then after 10 seconds everything comes back 

EXPECTED RESULT
No screen blacking out

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Host machine:  Lenovo H130-15AST laptop
Media player tested with: Brave Browser
Comment 1 Mahbod Karamoozian 2024-03-09 00:35:42 UTC
Edit: you may have to wait more than 10 seconds (about 30) to see the screen come back to normal
Comment 2 Patrick Silva 2024-03-09 21:35:33 UTC

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