When I put my computer to sleep while a game is running fullscreen through Proton, resuming causes a weird state: the lock screen is actually active and grabbing all keyboard/mouse input, but visually the fullscreened game is still showing on top of it. So I can see the game but can't do anything, and I can't see the lock screen to type my password either. Usually ends up needing a hard reboot.
Would be great if Proton could unfullscreen the game before suspend, similar to how some native fullscreen apps handle this, so the lock screen can actually render and take input properly on resume. You'd just refullscreen manually after unlocking.
Hello @Psyke1234, this reads like an issue with your desktop environment and/or compositor. This isn't something that Proton should need to bend over backwards to mitigate. Run your findings past the Budgie maintainers.
When I put my computer to sleep while a game is running fullscreen through Proton, resuming causes a weird state: the lock screen is actually active and grabbing all keyboard/mouse input, but visually the fullscreened game is still showing on top of it. So I can see the game but can't do anything, and I can't see the lock screen to type my password either. Usually ends up needing a hard reboot.
Would be great if Proton could unfullscreen the game before suspend, similar to how some native fullscreen apps handle this, so the lock screen can actually render and take input properly on resume. You'd just refullscreen manually after unlocking.
GPU + driver: AMD Radeon 760M (Framework 13), amdgpu kernel driver
Distro: Solus
Desktop environment + X11/Wayland: Budgie, X11