Bug 463017 - Moonlight's (SDL) power inhibit doesn't prevent screen sleep
Summary: Moonlight's (SDL) power inhibit doesn't prevent screen sleep
Status: RESOLVED DUPLICATE of bug 486506
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.26.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-13 17:19 UTC by Wyatt Childers
Modified: 2024-07-31 18:16 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wyatt Childers 2022-12-13 17:19:43 UTC
SUMMARY
Moonlight while playing a game sends inhibition signals to prevent monitor sleep (which is reported by power management in the status tray), however, if playing a game with a controller, monitors go to sleep.


STEPS TO REPRODUCE
1. Open moonlight
2. Play a game on a remote PC using a controller

OBSERVED RESULT
The monitors go to sleep as if no activity has been detected.

EXPECTED RESULT
The monitors stay on.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 6.0.11-300.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 62.0 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: ASUS

ADDITIONAL INFORMATION

I *think* this started with 5.26, but I can't be sure.

Moonlight requires two computers, so this might be hard to test. It's probably better to do whatever they're doing which appears to be power inhibition via SDL https://github.com/moonlight-stream/moonlight-qt/blob/411998d4e39f11ce6d3d8fc60657b699b19d5dd1/app/streaming/session.cpp#L1575
Comment 1 Wyatt Childers 2024-05-18 04:07:18 UTC

*** This bug has been marked as a duplicate of bug 485376 ***
Comment 2 Nate Graham 2024-07-31 18:16:30 UTC

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