this post was submitted on 30 Mar 2024
24 points (100.0% liked)
Linux Gaming
15312 readers
6 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME
away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't have an answer for you, but out of curiosity, is the freeze exactly 25 seconds? Because if so, it suggests that something is waiting for a dbus response that never arrives. Maybe a desktop portal request, for example. (The dbus timeout defaults to 25 seconds, IIRC.)
Also, while it's frozen, you might want to check beneath all the open windows to see if a new window has appeared behind them. It's possible that Steam opened a dialog box that's waiting for you to respond to it, but it somehow didn't get brought to the front.
Possibly? How would I do some dbus debugging to confirm that?
I don't think this is it, because when the UI unfreezes I often move the window around because it goes into drag mode and don't see anything behind it.
The freeze behaves like, I get a message and I open it to respond and maybe get a letter or 2 types before it just hard freezes.
man dbus-monitor
I would confirm that it's 25 seconds first, to avoid a possible wild goose chase.
In case you don't know, the main Steam issue tracker lives here:
https://github.com/ValveSoftware/steam-for-linux/
...and the Steam Flatpak issue tracker lives here:
https://github.com/flathub/com.valvesoftware.Steam/
Did you set the correct permissions?
How would permission affect freezes?
What permissions would I have to set?