Launcher (third-party flatpak) does not start on Steam Deck

[akikivirinta-commits]

As it comes as a flatpak it should work out of the box. Now I don't have even idea how to start debugging it. Fs-uae itself seems to work just fine but is rather annoying to use without the launcher.

[FrodeSolheim]

Hi, the flatpak isn't mine, and I don't how how it is packaged and what kind of mistakes would case the Launcher to not start. I'm afraid you have to try to find the maintainer of the flatpak and file a bug report with them first.

[akikivirinta-commits]

Guessed as much. "Assistant" of the package manager Discovery told to me complain here when I left a review that doesn't start. Now I need to find out who made the flatpack.

Meanwhile I downloaded the linux packages from fs-uae.net and that starts and otherwise is usable but weirdly that crashes when browsing folders so I cannot input roms or discs. That one is because of mismatching Qt libraries. That I can hopefully debug somehow.

[FrodeSolheim]

I got another report on eab about another user who was a similar qt library mismatch (https://eab.abime.net/showthread.php?t=121295), but possibly not quite the same since I don't that error was trigger by the file dialog.

I managed to reproduce the same? or some similar crash as you have by deleting the bundled glib/gtk libraries. This caused the Qt file picker to be used instead of the GTK one, and then PyQt crashed here as well.

By running strace ./fs-uae-launcher 2>&1 | grep Qt6

I noticed that it tries to load /lib/x86_64-linux-gnu/libQt6Svg.so.6 (and pdf) (from system! instead of the bundled libs), so that's probably the problem. I see that I blacklisted libQt6Pdf.so.6 / libQt6Svg.so.6 from being bundled. I don't recall why that was done, possibly just to reduce the install size because I didn't need that functionality, but then it seems that qt file picker does (presumably for file previews?), and I did not account for Qt trying to load this from the system dir.

So I probably need to do at least one of the following:

• Remove the blacklist so libQt6Svg.so.6 / libQt6Pdf.so.6 is included in _internal/
• Also remove libqpdf.so and libqsvg.so from_internal/PyQt6/Qt6/plugins/imageformats/ and libqsvgicon.so from _internal/PyQt6/Qt6/plugins/iconengines

You can actually try the latter: Delete the bundled file _internal/PyQt6/Qt6/plugins/iconengines/libqsvgicon.so - I suspect that might fix the problem until I've sorted it out properly?

[FrodeSolheim]

Please try https://www.dropbox.com/scl/fi/xusiqwjv6fu7medtimj8u/FS-UAE-Launcher_3.2.35-1_Linux_x86-64.tar.xz?rlkey=9imipa69bpnw3hf4pu9gghwd5&e=1&st=b9arwiy6&dl=1

[akikivirinta-commits]

I actually went around the problem by installing an older version of launcher and using that to do the setup. Since it uses the same database (it seems) I can now just use the new launcher to launch. I'll test this as soon as I'm able to. Thanks!