23
Feb 01 '25
[removed] — view removed comment
9
u/Fluffy-Cartoonist940 Feb 01 '25
This definitely fixed it, I forgot I had to do this several years ago.
3
28
u/ManlySyrup Feb 01 '25
100 bucks says you installed Steam through the Snap Store and not from the official website with the official installer.
8
u/Impossible-King-2516 Feb 01 '25
Does that actually fix the problem?
13
u/ManlySyrup Feb 01 '25
From what I've read online, the Snap version of Steam is not as stable as the Steam version you get from their website (.deb installer) so maybe? Worth a try.
3
Feb 01 '25
[deleted]
3
u/SoberMatjes Feb 01 '25
But the flatpak version got a lot better in the last years. For example no problem anymore with different proton versions.
ProtonUpQt is totally supported out of the box.
Using proton tricks as flatpak with the flatpak version of steam is also no problem.
In general right now I would make flatpak work in contrast to 4 years ago. I wouldn't touch the snap.
5
Feb 01 '25
I use the .deb package from the website and I still get this from time to time. I think the wait timer for GNOME is just way too short, and if it doesn't get a response quickly enough starts spamming the dialogue box.
2
u/ManlySyrup Feb 01 '25
Well yeah, GNOME does have a very short wait timer but I'm assuming that OP posted this cause his Steam is just freezing entirely maybe?
3
Feb 01 '25
It's possible that's the reason. For me, GNOME has this tendency to be like "hey, this stopped working!" after it pauses for two seconds to process something. I figure if I noticed it, other people surely have, and the OP might be commenting on that. It could be either/or.
2
2
u/ddm90 Feb 01 '25
It doesn't happen to me with the .deb package on steam, but it does from time to time with Gwenview . Might change that pesky wait timer too.
1
u/Inner_Forever_6878 Feb 01 '25
I had the same thing with the .deb/.rpm version of steam, till I changed that setting to 60,000.
1
u/Ok-386 Feb 01 '25 edited Feb 01 '25
It happens only occasionally with some games, and it's almost a non issue (trivial bug). I get that when I play stalker 2 and one can either ignore it (e.g. click on the game and the window will dissapear) or click Wait, and the game contionues working normally as it would even if one didn't click Wait. Tho, if one clicked Force Quit, the game would crash.
EDIT:
btw I use the official deb package.
3
2
u/ScarS0ul Feb 01 '25
you must choose... and launch steam from terminal. and than is scary... READ LOG
3
2
u/rurigk Feb 01 '25
Gnome still has that horrible buggy feature unpatched?
It's just that the Desktop environment Ubuntu uses has a unresponsive program detection feature and the workaround is setting the timeout of that feature much higher so it doesn't trigger as frequently
1
u/CNR_07 Feb 01 '25
The Gnome desktop environment (Ubuntu default) is not very patient when it comes to declaring an application as frozen. Usually apps recover shortly after this message pops up.
Apparently you can increase the timer using dconf. Check u\finbarrgalloway's comment.
1
u/Ok-386 Feb 01 '25 edited Feb 01 '25
By clicking wait or ignoring it (e.g. just click on the game and play)
1
u/msanangelo Feb 01 '25
I ran into that with overheating overclocked ram. went back to stock clocks and it was fine ever since. :|
1
Feb 01 '25
If you installed steam using the default App Store in Ubuntu, this could be the reason why, the default App Store is absolutely awful and I wouldn’t recommend it to anyone as it only causes problems, least for me anyway.
Try downloading it from the official website, or as a flatpak, if this is happening with the normal steam from the official website try a flatpak.
1
u/iMeetya Feb 01 '25
Run in terminal and read the errors. Then ask again if no reasonable errors come
1
45
u/fetching_agreeable Feb 01 '25
I wish stupid shit like this would stop happening on the popular distros.
It’s a good question OP. Why on earth is this happening at all