Wake host display(s) on connect instead of erroring out

[drws]

Is there an existing issue for this?

• I have searched the existing issues

Is your issue described in the documentation?

• I have read the documentation

Is your issue present in the nightly release?

• This issue is present in the nightly release

Describe the Bug

Sunshine currently fails to initialize a session when host display is turned off. This is easy to solve for a great majority of cases by issuing a DPMS turn on command such as xset dpms force on. This could and should be automatic and built-in, possibly configurable (if there are use cases) in Sunshine and/or Moonlight.

Expected Behavior

Sunshine should know the simple operation of turning on display instead of relying on the user to manually ensure for the display to be turned on when a remote session is wanted. Especially since Moonlight also supports Wake-on-LAN and turning on display seems an even more frequent case

Additional Context

No response

Host Operating System

Linux

Operating System Version

Debian 12

Architecture

64 bit

Sunshine commit or version

0.23.1

Package

Linux - deb

GPU Type

none (software encoding)

GPU Model

Intel

GPU Driver/Mesa Version

i915

Capture Method (Linux Only)

No response

Config

Default configuration.

Apps

No response

Relevant log output

Moonlight reports the following error on connection try:

Host returned error. Failed to initialize video capture/encoding. Is a display connected and turned on? (Error 503)

[vvuk]

This would be great; took me a while to figure out what was happening and also how to recover. In my case at least (i915), I have to both xset dpms force on and restart the sunshine service. Then I'm able to connect. So beyond just kicking a monitor on, sunshine may need to also reinitialize capture.

[t184256]

What's even worse, I can't seem to bind waking up the display to a global_prep_cmd or an app one, because it errors out before triggering the command =(

[Damglador]

Is there a way to kick display on with on Plasma Wayland?

[treierxyz]

If you have SSH access, you can run qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.wakeup on the Sunshine host machine to wake up Plasma Wayland. As @t184256 mentioned, you can't add this to the Sunshine prep commands as they don't run before the error occurs.

[Damglador]

Got ssh working, command works perfectly. Now time to figure out how to make a script for it and add it on my launcher with Termux. Thank you very much🤝

[t184256]

Just wiggle the mouse already. Sunshine creates the device anyway, how hard would it be?

[Damglador]

Well, how to wiggle a mouse if I can't connect to the system with Moonlight?

I was thinking about using KDE Connect, but it doesn't work through ZeroTier

[ReenigneArcher]

I believe they are suggesting that Sunshine should "wiggle the mouse".

[t184256]

I just wrote a tiny Python uinput script that monitors logs and wiggles when it sees errors: https://github.com/t184256/nix-configs/blob/58c4fd303a12a69f33f99f72f7263e1b2b5b8e92/nixos/services/sunshine.nix#L29 But I was addressing sunshine developers, really. Sunshine has all it needs (virtual mouse device included), but the will to do the wiggle.

[ReenigneArcher]

Feel free to submit a PR. The very few of us actually working on Sunshine don't have time to work on everyone's requests.

[drws]

And in such case please use proper calls, not actual wiggling :)