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:
<span style="color:#323232;">GetWin32Stats: display was not open yet, good
</span><span style="color:#323232;">GetWin32Stats: display was not open yet, good
</span><span style="color:#323232;">steamwebhelper.sh[5479]: Runtime for steamwebhelper: defaulting to /home/dirk/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
</span><span style="color:#323232;">steamwebhelper.sh[5479]: Running under Flatpak, disabling sandbox
</span><span style="color:#323232;">steamwebhelper.sh[5479]: CEF sandbox already disabled
</span><span style="color:#323232;">CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
</span><span style="color:#323232;">src/steamUI/steamuisharedjscontroller.cpp (540) : Failed creating offscreen shared JS context
</span><span style="color:#323232;">src/steamUI/steamuisharedjscontroller.cpp (540) : Fatal assert; application exiting
</span><span style="color:#323232;">08/18 23:36:47 Init: Installing breakpad exception handler for appid(steam)/version(1690583737)/tid(5473)
</span><span style="color:#323232;">assert_20230818233647_29.dmp[5780]: Uploading dump (out-of-process)
</span><span style="color:#323232;">/tmp/dumps/assert_20230818233647_29.dmp
</span><span style="color:#323232;">dirk ~ $
</span><span style="color:#323232;">assert_20230818233647_29.dmp[5780]: Finished uploading minidump (out-of-process): success = yes
</span><span style="color:#323232;">assert_20230818233647_29.dmp[5780]: response: CrashID=bp-9ef905ea-c25f-429b-9f2a-2ce832230818
</span><span style="color:#323232;">assert_20230818233647_29.dmp[5780]: file ''/tmp/dumps/assert_20230818233647_29.dmp'', upload yes: ''CrashID=bp-9ef905ea-c25f-429b-9f2a-2ce832230818''
</span>
I also tried flatpak run com.valvesoftware.Steam --reset again as it allowed me to start Steam once. But no, same result. Hangs for quite some time at the first GetWin32Stats: display was not open yet, good and circa the same duration onn CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize and 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 …
<span style="color:#323232;">$ flatpak list
</span><span style="color:#323232;">Name Anwendungskennung Version Zweig Installation
</span><span style="color:#323232;">Pixelorama com.orama_interactive.Pixelorama 0.11.1 stable system
</span><span style="color:#323232;">Steam com.valvesoftware.Steam 1.0.0.78 stable system
</span><span style="color:#323232;">Airshipper net.veloren.airshipper 0.10.0 stable system
</span><span style="color:#323232;">Freedesktop Platform org.freedesktop.Platform 22.08.14 22.08 system
</span><span style="color:#323232;">i386 org.freedesktop.Platform.Compat.i386 22.08 system
</span><span style="color:#323232;">Mesa org.freedesktop.Platform.GL.default 23.1.4 22.08 system
</span><span style="color:#323232;">Mesa (Extra) org.freedesktop.Platform.GL.default 23.1.4 22.08-extra system
</span><span style="color:#323232;">nvidia-535-98 org.freedesktop.Platform.GL.nvidia-535-98 1.4 system
</span><span style="color:#323232;">Mesa org.freedesktop.Platform.GL32.default 23.1.4 22.08 system
</span><span style="color:#323232;">Mesa (Extra) org.freedesktop.Platform.GL32.default 23.1.4 22.08-extra system
</span><span style="color:#323232;">nvidia-535-86-05 org.freedesktop.Platform.GL32.nvidia-535-86-05 1.4 system
</span><span style="color:#323232;">nvidia-535-98 org.freedesktop.Platform.GL32.nvidia-535-98 1.4 system
</span><span style="color:#323232;">openh264 org.freedesktop.Platform.openh264 2.1.0 2.2.0 system
</span>
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.
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.
DeeBeeDouble