Since some time now the Steam Flatpak cannot start up and I have no idea why this happens.
Web research leads to basically nothing that is related to what I experience so I assume it has something to do with my system. Other Flatpaks start up normally and I can use them.
When resetting everything related to the Steam Flatpak and reinstalling it from Flathub it loads and installs the Flatpak and then installs all necessary stuff
[various update-related stuff]
setup.sh[4598]: Forced use of runtime version for 32-bit libcurl.so.4
setup.sh[4598]: Found newer runtime version for 32-bit libSDL2-2.0.so.0. Host: 0.2400.0 Runtime: 0.2600.5
setup.sh[4598]: Forced use of runtime version for 32-bit libgtk-x11-2.0.so.0
setup.sh[4598]: Found newer runtime version for 32-bit libvulkan.so.1. Host: 1.3.224 Runtime: 1.3.239
setup.sh[4598]: Forced use of runtime version for 32-bit libdbusmenu-glib.so.4
setup.sh[4598]: Forced use of runtime version for 32-bit libcurl-gnutls.so.4
setup.sh[4598]: Forced use of runtime version for 32-bit libdbusmenu-gtk.so.4
setup.sh[4598]: Forced use of runtime version for 64-bit libcurl.so.4
setup.sh[4598]: Found newer runtime version for 64-bit libSDL2-2.0.so.0. Host: 0.2400.0 Runtime: 0.2600.5
setup.sh[4598]: Found newer runtime version for 64-bit libvulkan.so.1. Host: 1.3.224 Runtime: 1.3.239
setup.sh[4598]: Forced use of runtime version for 64-bit libcurl-gnutls.so.4
steam.sh[2]: Steam client's requirements are satisfied
So everything looks good up to this point. The small Steam update windows poppend up several times indicating the running installation/update. The output then continues:
[2023-08-17 22:47:50] Startup - updater built Jul 28 2023 18:44:09
[2023-08-17 22:47:50] Startup - Steam Client launched with: '/home/dirk/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/steam' '-no-cef-sandbox'
08/17 22:47:50 Init: Installing breakpad exception handler for appid(steam)/version(1690583737)/tid(5467)
[2023-08-17 22:47:50] Loading cached metrics from disk (/home/dirk/.var/app/com.valvesoftware.Steam/.local/share/Steam/package/steam_client_metrics.bin)
[2023-08-17 22:47:50] Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults
[2023-08-17 22:47:50] Using the following download hosts for Public, Realm steamglobal
[2023-08-17 22:47:50] 1. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2023-08-17 22:47:50] Verifying installation...
[2023-08-17 22:47:50] Verification complete
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf0d328f0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xf0d311c0
GetWin32Stats: display was not open yet, good
GetWin32Stats: display was not open yet, good
(The last line gets printed twice, yes.)
The first startup process then hangs there for a few seconds and continues with this.
steamwebhelper.sh[5473]: Running under Flatpak, disabling sandbox
steamwebhelper.sh[5473]: CEF sandbox already disabled
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
src/steamUI/steamuisharedjscontroller.cpp (540) : Failed creating offscreen shared JS context
src/steamUI/steamuisharedjscontroller.cpp (540) : Fatal assert; application exiting
08/17 22:48:39 Init: Installing breakpad exception handler for appid(steam)/version(1690583737)/tid(5467)
assert_20230817224839_27.dmp[5771]: Uploading dump (out-of-process)
/tmp/dumps/assert_20230817224839_27.dmp
dirk ~ $
After the command prompt is shown agein, this gets printed:
assert_20230817224839_27.dmp[5771]: Finished uploading minidump (out-of-process): success = yes
assert_20230817224839_27.dmp[5771]: response: CrashID=bp-f62fb7e8-d024-452e-a937-9c6672230817
assert_20230817224839_27.dmp[5771]: file ''/tmp/dumps/assert_20230817224839_27.dmp'', upload yes: ''CrashID=bp-f62fb7e8-d024-452e-a937-9c6672230817''
At the given location there is no dump file.
Do you guys have any Idea why this happens and how I can fix it?
Involved software:
$ flatpak --version
Flatpak 1.15.4
$ flatpak remotes
Name Optionen
flathub system
$ flatpak info com.valvesoftware.Steam | grep Version | awk '{print $2}'
1.0.0.78
$ uname -rms
Linux 6.4.10-arch1-1 x86_64
$ openbox --version | head -n1
Openbox 3.6.1
$ pacman -Qi xorg-server | grep Version | awk '{print $3}'
21.1.8-2
Okay, well then we'll need to investigate further.
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-datato 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 ofwill also do the trick. That, just as a small side note.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.Thanks for your help!
Okay, not it gets weird. I uninstalled Steam with deleting the data. Then I reinstalled it and now does die the double
GetWin32Stats: display was not open yet, goodwith several seconds of “hangign” again after all the initialization stuff and it then crashes again as described but in addition to that it also now hangs for several seconds atCAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize.The weird thing is: now I can’t even start/reset it with
flatpak run com.valvesoftware.Steam --resetanymore.This unfortunately makes no difference.
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.08And then install it again with
flatpak install org.freedesktop.Platform/x86_64/22.08To 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.
I am using Pixelorama and Airshipper as Flatpaks without any issues. The only application that does not work is Steam.
I could not uninstall it because Pixelorama and Airshipper needed it (as well as Steam, of course). So I removed all of them before, then removed the package and reinstalled it. Then I started up Steam and it crashed again with the same error message and behavior. It loaded Steam, the update messages were shown, the steam popups popped up, but at the end, well, this again:
I also tried
flatpak run com.valvesoftware.Steam --resetagain as it allowed me to start Steam once. But no, same result. Hangs for quite some time at the firstGetWin32Stats: display was not open yet, goodand circa the same duration onnCAppInfoCacheReadFromDiskThread took 0 milliseconds to initializeand them mentions a nonexistent log file.I wonder if there is a clean way to thoroughly remove all and everything coming from Flatpak. At this point I don’t even care if there is any data lost ...
Yeah ... And it even makes no sense either. It started up before and let me log in but the next start it crashed and now it always crashes no matter what I do. There seems also no-one else in the world affected by this.
All this is seriously so weird...
Okay, so the runtimes were fine, good to know. Btw, you can remove runtimes without first removing the apps that depend on them. They just won't work any more until you install it again.
Not an official one, but this should do the trick if you really want to delete everything. If you want to, you could back up the user files for your other Flatpaks first.
1.
flatpak uninstall --all --delete-data2.Remove flatpak with your package manager
3.
sudo rm -rf /var/lib/flatpak /var/cache/flatpak ~/.local/share/flatpak ~/.cache/flatpak ~/.local/share/flatpak ~/.cache/flatpak /etc/flatpak4.Reboot
5.Install flatpak again
6.Add flathub
7.Install steam
If that also doesn't work, I'm 95% certain it has to be one of your system packages. Weird that a system package would break any Flatpaks though... What distro are you using anyway?
I tried first, but it just complained that Steam (and the other two Flatpaks) needed the package and it aborted the removal process.
Anyways, I uninstalled all Flatpaks as you described, removed the directories, removed the Flatpak package, did a reboot, ran a full system update and installed Flatpak and did another reboot just to be sure and just installed Steam this time.
It starts getting hilarious. Same, Friggin. Result. Installation works without any issues, update works without any issues, the popups show, the console output looks fine, and then this again at the end:
Since everything regarding Flatpak was removed, including all caches, configuration files and data I am pretty sure that it has to do something specificially with the Steam Flatpak because my system as a whole works properly and and all other Flatpaks I have installed also work properly …
I’m on Arch. I have listed all involved application’s version numbers at the end of my original post.
Edit: Not sure if it helps, but here’s the full installation/update output:
https://nopaste.net/QJI3c2Amz5
That is also possible. But then why is it working for everyone else? I used the steam flatpak multiple times today with no issues. I guess you could also ask the same question for the system package issue theory.
How about the package manager version? Is that working? That could give some hints on whether it's the system or the Flatpak package.
Arch, yes. This is what all the people who had to remove xdg Desktop portal use. How could they remove it if it's a dependency of flatpak? Maybe they don't have flatpak.
If you have too much time on your hands, you could try another fresh arch installation on another hard-drive. If it works there, we know it has to be a system package. If it doesn't, it's probably the Flatpak.
That’s the question here :) Flatpak it self can’t be the issue because other Flatpaks work. My system can’t be the issue because my system works. And yes, the Steam Flatpak on it’s own also can’t be the issue because then more people would be affected and I would find something during web research.
There isn't really a Steam version in the repos but only in multilib. So I enabled it and installed steam from there. It also crashes. The only difference is that there are some fontconfig things it cannot understand.
So it's Steam in combination with my system. This time the mentioned dump is there but it does not contain any information I could use/understand.
When reinstalling Flatpak it asked for xdg-desktop-portal-impl to be installed and offered multiple packages that provide it.
It also worked earlier during testing (at least one time it started up and let me log in but subsequently it crashed on any of the further tries) so all dependencies are satisfied.
Okay... Now that you have the non flatpak steam, could you remove flatpak and xdg-desktop-portal*?
Reboot and launch steam again.
This is the last idea I have for now... If this also doesn't help, it is probably a different issue than this and this, and you should report it to valve.
Thanks for all your help with this. Unfortunately Steam still scrashes. The xdg-pdesktop-portal packages aren’t installed. Only the Flatpak package seems to have them as hard dependency.
Valve said they won’t give any support here because I’m not using Ubuntu with Gnome.
So no more Steam games for me, I guess …
This just can't be...
After some deep digging, I found one last Idea. Try launching steam with the
-vguiflag and let me know if that works.Yep. This makes no sense at all. But I have no idea what to try anymore.
Unfortunately this does not change the behavior. It still does the same thing as described before.
Well that's that then. I also have no idea what to try anymore... I guess you'll just have to wait until some random update fixes the issue. Sorry.
Edit: Since you reinstalled everything, I think it could be some cache on your system that went bad. That would explain why both the Flatpak and native versions don't work and why the rest of your system works. But I have no idea where that cache might be...
Yep ... It magically broke so it hopefully will magically be fixed 😀
Thanks for all your support on this!