When starting up stream and along side a game, it will sometimes make every application crash and unresponsive then the OS will lock up, any reason why this happens? Specs OS Ubuntu 23.04 Gnome 44.2 AMD rx6700xt Ryzen 5 5600xt 16GIB Kernal 6.2 Generic Wayland 64-bit ASUSTeK COMPUTER INC. ROG STRIX B450-F GAMING II Firmware 5003
Can’t comment on the cause, but I’ve found a workaround for this by launching steam from the terminal. I suppose that the gnome launcher calls a different version or uses some specific parameters.
I’ll check it when I’m less lazy (hmmm)
Would like not to use the terminal, I try my best to stay away from it at all cost
Understandable.
You can set up a keyboard shortcut, which runs off the terminal commands, then you’re always using it but not using it, also
deleted by creator
???
forgot the attachment, i’ve sent another post
doubt this will do anything, but have you tried turning this on?
(posted again because the edit didn’t federate and i forgot the attachment)Looks like lemmy doesn’t accept posts with attachments.
I tried to send a screenshot of a settings for accelerated rendering in steam. I don’t think i’ll make a difference, but turning it on is worth a tryI’ve had better luck using the Flatpak version of Steam than either the repo version or downloaded from Steam. On 22.04 I could not get the Gnome launcher to work at all for either and had to use the terminal. No issues using the Flatpak version. It also works with Proton-Up, which is also available as a Flatpak.
As for your issue specifically, you could look at the logs, but the only way I know to do that is via the Terminal, and you mentioned you don’t want to do that.
Idk if it logs it as the system would just hard crash and i had to do a full restart either by pulling the plug out or holding down the button
It will most definitely be logged if it’s Gnome crashing. If the entire system is crashing that’s a very different story, and if you’re hard resetting it sounds like a system crash, not Gnome specifically. Depending on how it crashes, there may be logs.
I started it up using terminal with logs, but I’m stuck again :/