DeeBeeDouble

I'm starting to think that your flatpak runtimes might be corrupted.

You can try reinstalling the one used by steam. Uninstall with

flatpak remove org.freedesktop.Platform/x86_64/22.08

And then install it again with

flatpak install org.freedesktop.Platform/x86_64/22.08

To eliminate any other potential issues I'd recommend deleting the steam user folder as well before launching it again. Like I told you earlier.

Edit: It's hilarious, I find many people having the exact same issue but never with the Flatpak version. Some even use the Flatpak version as a workaround. Very weird.

Okay, well then we'll need to investigate further. 

On one page I found a set of rm commands for resetting Steam issues and adapted it to the Flatpak version.

While these commands will delete most of the steam stuff, just in case you didn't know, for any flatpak you can run flatpak uninstall --delete-data to delete all user data for uninstalled apps. Or, if you don't want to uninstall the app first, just deleting ~/.var/app/the app you want to delete the data of will also do the trick. That, just as a small side note.

Resetting it like this seems to work a bit. The Steam interface started up one time and after logging in and restarting it, it now does the same thing as before.

That's something at least. Why don't we try something? Maybe the beta version will fix it? When you have the steam client open, try switching to the beta version of it. You can do that by opening the steam settings, go to interface and select the beta. If that also doesn't work, try launching it with -no-cef-sandbox, as that also fixed it for some people.

Did you also delete the steam user data when reinstalling it? Regardless, I found a Github issue that looks very similar to yours. Apparently this was caused by a beta update? But this was about 4 months ago? Weird.

Anyway, the suggested fix was to first reset steam with flatpak run com.valvesoftware.Steam --reset And then opt out of any potential beta: com.valvesoftware.Steam -clearbeta

Not sure if this really is the same issue, but it's definitely worth a try.

Edit: Seems like on some systems, removing the package xdg-desktop-portal-gnome also fixed it. Don't know if it also applies to the flatpak, but just try it. Just remember to install the package again if it doesn't fix it. It may be needed for some other things.

Funny, I remember getting the exact same comment on Reddit when it was still there. While this is obviously correct, to me, it just feels wrong to use Discord in a browser. Also, other clients offer functionality that not even Discord in a browser supports. But for those who don't mind or don't need those extra features, it's a great solution, no doubt.

I think librewolf only changes some settings in your user profile. So if you were to copy it to Firefox, it would be exactly the same as Librewolf. But keep in mind that updates to Firefox might require an updated Librewolf profile that you wouldn't be getting. So I guess you would slowly lose all the Librewolf changes. But like I said, I'm not sure, so I could be wrong.

You help where you can

I did. I know the guy.

What? You mean I'm Err404UNameNotFound? I'm not.

Very true. There are obviously some community projects, but no doubt, official software would be better. Or even better, if they would make it easy for the community to develop those tools.

They are no longer on reddit. If I hadn't reposted them here, they would have been lost forever.

I know, right? It's funny how all of my posts here so far are just old ones from Reddit...

You're welcome! 

Just make sure to grab the Xenia canary version as it has many improvements for wine.

Also, in most cases, setting the renderer to Vulkan can improve things. You can do so by creating a text file called "portable.txt" in the Xenia directory, and then run Xenia again. This will create a config file in the Xenia directory, in which you can then tell Xenia to use Vulkan.

Lastly, I'd recommend using bottles for all that as it makes everything much easier.