Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Win 10 does not wake from sleep after streaming Sunshine to Nvidia Shield over LAN #1809

Closed
3 tasks done
maxwell2027 opened this issue Nov 2, 2023 · 2 comments
Closed
3 tasks done
Labels

Comments

@maxwell2027
Copy link

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

Win 10, after streaming Sunshine to Nvidia Shield over LAN, then putting PC to sleep, if I try wake up PC, it hangs then reboots.

To rectify, before putting PC to sleep, I have to restart the SunshineService service in task manager after streaming.

This issue does not occur if streaming Sunshine over WIFI.

This issue has been ongoing since I first installed Sunshine about a year ago. Still happens with latest releases.

Expected Behavior

Win10 should wake up after sleep, and not reboot, after streaming over LAN and then putting PC to sleep.

Additional Context

No response

Host Operating System

Windows

Operating System Version

10

Architecture

64 bit

Sunshine commit or version

0.21.0

Package

Windows - installer

GPU Type

Nvidia

GPU Model

RTX 3080

GPU Driver/Mesa Version

546.01

Capture Method (Linux Only)

No response

Config

sunshine_name = SUNSHINE-PC
resolutions = [
    1920x1080,
    3860x2160,
    2560x1440
]
gamepad = ds4
min_log_level = 2
hevc_mode = 0
fps = [60,90,120]

Apps

No response

Relevant log output

N/A
@LizardByte-bot
Copy link
Member

It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!

@LizardByte-bot
Copy link
Member

This issue was closed because it has been stalled for 10 days with no activity.

@LizardByte-bot LizardByte-bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants