Usually we aren’t out of commission for too long.
Bad news on that front, from Lemmy General Matrix chat:

Usually we aren’t out of commission for too long.
Bad news on that front, from Lemmy General Matrix chat:

Oh yeah, that will do it. There's a script by a Valve employee (it's linked in the sticky troubleshooting post) that checks stuff like that.
Sometimes the site can get sluggish and API responses fail if the site is being hit particularly hard by scrapers. I'll dig into the logs when I get the chance, but for now I've enabled a DDoS protection setting. Can you try now? This is the best idea I have atm for what's causing this.
Is SteamVR running on the computer?
I'm able to log into voyager just fine, does it tell you more about the error or is it just a timeout message?
Yeah, I expected the scroll to work the same. The current desktop integration seems really half-baked.
See my other reply, turns out the issue is Flatpak and probably Steam input.
I did some more testing and they only apply when you're in 'Gamepad mode'. Otherwise you're stuck with the default pointier mappings, which only uses one controller while the desktop one can use both.
Also I found out that the controller config does apply to apps launched from the plus menu (when you're in gamepad mode), but this doesn't work for Flatpak apps (sandboxing issue presumably).
Don't you hate it when you're trying to make out with your girlfriend but all her Damocles get in the way.
Why does everyone who starts using AI always devolve into posting like this?
Note, this is a statement by a member of the Green Party, not the party itself.
This got rid of it for me:
cd ~/.local/share/applications
cp /usr/share/applications/org.chromium.Chromium.desktop .
sed -i "$ a Hidden=true" org.chromium.Chromium.desktop