Closed RyanHakurei closed 1 year ago
Opted into Steam client beta?: Yes
this should be the problem. try revert to stable version.
Thanks for the report! I'm not sure if you have any form of accessing your Deck remotely, like SSH. But if so, would be really useful if you could collect the output of dmesg
and journalctl -b
and attach them here, when the issue reproduces.
Cheers!
Part of the issue I'm facing is that, after this occurs I restart the deck and attempt to load but due to having Clover boot manager (no other OS though) I'm unable to select through as there's no way to use the internal controls. While this is a modification issue layered ontop of the OS issue, unsure how to proceed as I don't know if it's possible to complete a flash/etc without having some form of controls.
Thanks for the report! I'm not sure if you have any form of accessing your Deck remotely, like SSH. But if so, would be really useful if you could collect the output of
dmesg
andjournalctl -b
and attach them here, when the issue reproduces.Cheers!
Thank you @RyanHakurei ! But it seems everything is fine due to the logs - did you collected them right after the issue?
Dmesg shows that the Deck was resuming from suspend. Also, if not a problem for you, please collect the full dmesg logs and attach it here instead of just a snippet - you could either attach the file in a comment or use some pastebin service.
Thanks!
Thank you @RyanHakurei ! But it seems everything is fine due to the logs - did you collected them right after the issue?
Dmesg shows that the Deck was resuming from suspend. Also, if not a problem for you, please collect the full dmesg logs and attach it here instead of just a snippet - you could either attach the file in a comment or use some pastebin service.
Thanks!
Logs were taken from the point of launching a game, Jul 30 21:26:19 Reisen systemd[1089]: Started app-flatpak-org.prismlauncher.PrismLauncher-8752.scope.
through the triggering of the bug. Dmesg still isn't showing anything of use. I think the issue is within the Steam client or Gamescope not the underlying OS.
Hello, I am also facing the same issue. Was using the stable channel when it started to happen, I also tested with beta channel and the problem is still happening.
Was able to fetch dmesg
and journal
logs using ssh
though.
Thank you @RyanHakurei ! But it seems everything is fine due to the logs - did you collected them right after the issue?
Dmesg shows that the Deck was resuming from suspend. Also, if not a problem for you, please collect the full dmesg logs and attach it here instead of just a snippet - you could either attach the file in a comment or use some pastebin service.
Thanks!
In fact, this pretty consistently appears in the console_log when the error occurs. I am using Prism Launcher to trigger this as it's more consistent, but I can also get it to trigger with Borderlands 3.
Hi I have got my problem fixed by uninstalling all my plugins (except Porwer Tools and Vibrand Deck) and disabling "Updated fan control"
I have got this from Valve Support:
Hi,
Thanks for the information.
We recommend to disable "Enable updated fan control". Please follow the steps below:
Use the Steam button > Settings > System > and near the bottom of that page in the Advanced section you should see the "Enable updated fan control" setting.
Disable the setting.
Use the Steam button again > go to Power > select Restart
After the system restarts, retest the issue again.
Important: If disabling the "Enable updated fan control" setting fixes or improves the issue, please let us know.
If you are using any external plugins on your Deck, we also recommend that you temporarily disable all external plugins (some plugins have been known to cause severe performance issues) and retest to see if the problem still exists.
If you are still having the problem, please write back and we will assist further.
Steam Support
Deppy
Hoppe that this can also help you.
Noticed the same behavior on my Deck, beta or stable client. I've got devkit tools plugged onto it, so I'm gonna take a quick look at triaging this, but I do notice that this is reproducible by pressing the volume keys, even after a Steam client restart/reboot. As soon as the volume overlay disappears, the video goes black, while the system is still running behind the black screen.
If it is due to plugins or their settings, I'll bisect which one exactly is causing this.
deckfaqs
plugin, as included in the current repository of the SteamDeckHomebrew group's Decky Plugin database.. Removing this plugin caused the behavior to go away.So, it being that plugin, I'd suggest removing it, and then restarting your Steam Deck.
Unfortunately, this issue seems to be outside of the scope of the SteamOS repo, and might be closed.
Also, I can't say for sure a different plugin I don't have installed would cause this issue, either. It could be a behavior common to several plugins. I'll be looking into the code of deckFAQs to see where the trouble code sits.
Perhaps noteworthy: I'm not using a performance overlay set in the SteamOS settings.
I can reproduce and provide further information, logs, and run tests and debug as needed.
@RyanHakurei are you using any Decky Loader plugins? If so, could you share a list? And do you have DeckFAQs installed?
You can list all your installed plugins quickly with an ls ~/homebrew/plugins
from a command line.
@RyanHakurei are you using any Decky Loader plugins? If so, could you share a list? And do you have DeckFAQs installed?
You can list all your installed plugins quickly with an
ls ~/homebrew/plugins
from a command line.
I do, and when I get home I'll check my plugins
Yeah so I did have Deckfaqs installed, but as the other issue references this was fixed in 1.8.0 and I have since updated.
Your system information
Please describe your issue in as much detail as possible:
After existing a game I am presented with a blank screen. I can hear UI sound effects so everything is working behind the scenes, but the screen is not displaying anything. The only way I've found out of this is a hard reboot. Sometimes I can get the display to output something when I bring up the power menu, but this is very intermittent. PXL_20230729_225037454.TS.webm
Steps for reproducing this issue: