Cannot launch ProtonUp-QT on Steam Deck

[TigerBeanst]

Describe the bug
Try to launch ProtonUp-QT but it close quickly without seeing the GUI

To Reproduce
Launch it by menu or flatpak run net.davidotek.pupgui2

Expected behavior
Normally working

Screenshots

Desktop (please complete the following information):

• Platform: Steam Deck
• System: SteamOS 3.5.17
• Version: ProtonUp-Qt 2.9.0(Flatpak only has 2.9.0, not 2.9.1
• How did you install ProtonUp-Qt?: Discover app store

Additional context
None

Terminal output

(deck@TigerDeck ~)$ flatpak run net.davidotek.pupgui2
F: Not sharing "/esp" with sandbox: Ignoring blocking autofs path "/esp"
/app/bin/net.davidotek.pupgui2 3:     3 δ                  תpython3 -m pupgui2 "$@"
(139)(deck@TigerDeck ~)$

[sonic2kk]

Cannot reproduce on my Steam Deck. Did some permissions get messed up for your Flatpak? This warning is a general Flatpak message of some kind: F: Not sharing "/esp" with sandbox: Ignoring blocking autofs path "/esp" - Maybe some filesystem permissions got messed up? If you have a tool like Flatseal

Flatpak only has 2.9.0, not 2.9.1

What? I'm running ProtonUp-Qt 2.9.1 on my Steam Deck and my PC, 2.9.1 is available as a Flatpak. Although this issue is not specific to the ProtonUp-Qt version, it appears to be a Flatpak configuration issue.

ProtonUp-Qt Flatpak was bumped to v2.9.1 with flathub/net.davidotek.pupgui2@2e8b0a7.

[sonic2kk]

A quick Google search confirms this is a general Flatpak issue. One suggestion was to force disable Wayland and force enable X11. You can do this from the Plasma System Settings, Flatseal, or manually with a terminal command (streetpea/chiaki4deck#112 (comment)).

This --nosocket=fallback-x11 seems related to #284 (and thus #312, and flathub/net.davidotek.pupgui2#24). I guess maybe newer installs of Flatpaks are not too happy about some X11 stuff being set?

Note though that flathub/net.davidotek.pupgui2#24 sets --socket=fallback-x11, not --nosocket=fallback-x11. I'm not sure if --nosocket can be set in the manifest, but if it can, perhaps we can add that.

Looking at streetpea/chiaki4deck#263 (comment) it may also be caused by a Qt6 update (iirc comes from KDE Platforms). I'll run some updates and see if ProtonUp-Qt breaks as a result, and if tinkering to set --nosocket=fallback-x11 fixes the problem. If this Qt6 update is what broke things, then it's probably pretty widespread...

[sonic2kk]

It would also be interesting to know if the AppImage has the same problem

[sonic2kk]

Huh, when trying to update the KDE Platforms, it fails to pull Qt6.6, saying the commit it's looking for doesn't exist. This is a different commit than the one mentioned in the chiaki4deckk issue. Perhaps some Qt6.6 update was pulled because of this breakage?

Nevermind, restarting my Steam Deck worked. However even after the update, ProtonUp-Qt still works.

For what it's worth, revisiting your terminal output, it looks like the crash is happening before ProtonUp-Qt can even properly load.

[sonic2kk]

I tried fiddling with a bunch of ProtonUp-Qt permissions in Flatseal, including access to the whole filesystem, and and while I couldn't reproduce a crash I was able to reproduce the Not sharing /esp with sandbox message. ProtonUp-Qt still started normally after that, however.

I noticed your terminal after that message appears to return with a 139 exit code, which iirc is a segfault inside of a container (which makes sense for a Flatpak). This could still be coming from some fault with Qt, or maybe you need to re-install the Flatpak? This might also allow you to use an up-to-date ProtonUp-Qt version, as ProtonUp-Qt 2.9.1 is definitely available.

[sonic2kk]

I'm updating to Preview (reverted back a week or so ago for testing purposes) and I'll see if the issue is present there. I should've checked but I think Beta is on 3.5.17 now.

[sonic2kk]

Updated to Preview, checked that the version is 3.5.17, ProtonUp-Qt v2.9.1 still works for me, with the most up-to-date Platforms packages from Flathub as well. So I can't reproduce this on my Steam Deck or PC. My remaining advice would be:

• Try updating to v2.9.1, if you have to please try reinstalling.
• If there are any pending KDE Platforms / Qt6.6 Platforms updates pending in Discover, please run those as well.
• Try running the command to set --nosocket=fallback-x11 and seeing if that permission override fixes the problem for you, although I suspect not since this is possibly a segfault.
• Try resetting your Flatpak permissions, although again, possibly won't help if this is a segfault.
• See if the issue occurs on the AppImage.
• If you have a Linux PC, check if the issue also occurs there, to narrow down if this is specific to SteamOS somehow.

[TigerBeanst]

@sonic2kk

1

I'm running ProtonUp-Qt 2.9.1 on my Steam Deck and my PC, 2.9.1 is available as a Flatpak.

I install it using discover and look like there is only "shows" 2.9.0 at the website? https://flathub.org/apps/net.davidotek.pupgui2

(deck@TigerDeck ~)$ flatpak info --show-location net.davidotek.pupgui2
/var/lib/flatpak/app/net.davidotek.pupgui2/x86_64/stable/bd78742afc42ae3c7e947316850c15ff6599e543dc0bfd486f911c584e7f298f

(deck@TigerDeck ~)$ flatpak remote-info --log flathub net.davidotek.pupgui2
        ID: net.davidotek.pupgui2
       Ref: app/net.davidotek.pupgui2/x86_64/stable
      Arch: x86_64
    Branch: stable
Collection: org.flathub.Stable
  Download: 25.1 MB
 Installed: 96.2 MB
   Runtime: org.kde.Platform/x86_64/6.5
       Sdk: org.kde.Sdk/x86_64/6.5
    Commit: bd78742afc42ae3c7e947316850c15ff6599e543dc0bfd486f911c584e7f298f
    Parent: 90e5f68cb643946cf81baffc63fe68c08bcaab43472d8e477dbab8a55fbdc26a
   Subject: Release v2.9.1 (2e8b0a71)
      Date: 2024-01-09 22:20:17 +0000
   History:

Well, the commit match. (But it still shows 2.9.0 in website and Flatseal....)

2

About Wayland and X11

Have been try:

sudo flatpak override --nosocket=fallback-x11 --socket=x11 net.davidotek.pupgui2

or
disable socket=x11, enable socket=Wayland, enable socket=fallback-x11(I searched before)
in Flatseal.

All doesn't work.

3

I should've checked but I think Beta is on 3.5.17 now.

Nope...I am using all stable version (stable SteamOS, stable Steam client)

4

Try updating to v2.9.1, if you have to please try reinstalling.

I have been trying to uninstall it and install again. It doesn't work.

[TigerBeanst]

AppImage version works normally.

[sonic2kk]

I install it using discover and look like there is only "shows" 2.9.0 at the website?

Sounds like a problem with Flathub, Discover shows v2.9.1. The changelog it's showing is for v2.9.1 though: https://github.com/DavidoTek/ProtonUp-Qt/releases/tag/v2.9.1

Have been try: [override commands]

Damn.

Nope...I am using all stable version

Hm, it's possible but unlikely that the stable SteamOS has issues. I haven't used SteamOS Stable, well, ever for any length of time, so I'm not sure. I think this would also be more widely reported if it was specific to Stable.

AppImage version works normally.

Thanks for checking! It seems like this is specific to the Flatpak, and something specific to your Steam Deck, too. Did you try resetting the Flatpak permissions, such as from Flatseal?

[TigerBeanst]

Discover shows v2.9.1.

My discover shows 2.9.0 and the website shows 2.9.0 too...?
Maybe there is some version name that be forgotten to edit?

Did you try resetting the Flatpak permissions, such as from Flatseal?

Yes, and it doesn't work.

And I try something strange that I don't know if it is useful.

(deck@TigerDeck ~)$ cd /var/lib/flatpak/app/net.davidotek.pupgui2/current/active/files/lib/python3.10/site-packages/
(deck@TigerDeck site-packages)$ python3 -m pupgui2
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/var/lib/flatpak/app/net.davidotek.pupgui2/x86_64/stable/bd78742afc42ae3c7e947316850c15ff6599e543dc0bfd486f911c584e7f298f/files/lib/python3.10/site-packages/pupgui2/__main__.py", line 1, in <module>
    from pupgui2.pupgui2 import main
  File "/var/lib/flatpak/app/net.davidotek.pupgui2/x86_64/stable/bd78742afc42ae3c7e947316850c15ff6599e543dc0bfd486f911c584e7f298f/files/lib/python3.10/site-packages/pupgui2/pupgui2.py", line 8, in <module>
    from PySide6.QtCore import Qt, QCoreApplication, QObject, QThread, QWaitCondition, QMutex, QDataStream
ImportError: libQt6Core.so.6: cannot open shared object file: No such file or directory

Cause it before look likes something broken when runing python...

[sonic2kk]

Maybe there is some version name that be forgotten to edit?

Very strange, it's showing v2.9.1 for me... I did have a look to see if some strings weren't updated when I saw Flathub was mentioning the changelog as being for v2.9.0, but didn't find any. Maybe DavidoTek knows better though, I don't know a whole lot about how Flatpak packaging works.

ImportError: libQt6Core.so.6: cannot open shared object file: No such file or directory

This error is because of the Qt6 packages being missing, they come from the Flatpak environment and when you run directly like this, it looks for the Qt6 packages from your system, which of course the Steam Deck's Python installation does not have PySide6. 🙂 I didn't check but I assume the Steam Deck just has a vanilla Python installation, since Python is a dependency for Proton and only uses the standard library (it's also a dependency for the Steam Client but I'm not sure outside of Proton how the Client uses Python).

If it wasn't Qt6 erroring here, it would error about the plethora or other packages being missing.

[sonic2kk]

It may be possible to run the python3 -m pupgui2 the way you did, but by pointing to the Flatpak Python3 binary. I really don't know if this works or will yield anything useful, and it's not really a solution but more of an experiment.

I don't know where the binary is installed to (the paths are different on my PC which I'm currently on) but maybe something like this? /var/lib/flatpak/app/net.davidotek.pupgui2/current/active/files/bin/python3 - If this exists, you can check if you can run it with /var/lib/flatpak/app/net.davidotek.pupgui2/current/active/files/bin/python3 -v. I'm assuming the Python runtime is installed (or at least linked) per-flatpak, so there would be a Python binary of some kind bundled with the ProtonUp-Qt Flatpak (it certainly won't use the system one, but it may share Python runtimes, and so may symlink maybe? I don't think it comes from the Platforms specifically, anyway).

If you can find the Python binary, your above command would become something like this: cd /var/lib/flatpak/app/net.davidotek.pupgui2/current/active/files/lib/python3.10/site-packages/ && /replace/with/flatpak/path/to/python3 -m pupgui2

[sonic2kk]

Should also note that even if this is possible there might be other issues since this is still running outside of the Flatpak environment, so other libraries may be missing or incompatible (I think since SteamOS is on KDE this might be fine, but there might be some missing Qt6 stuff since it runs Plasma 5...)

[DavidoTek]

I install it using discover and look like there is only "shows" 2.9.0 at the website? https://flathub.org/apps/net.davidotek.pupgui2
Maybe DavidoTek knows better though, I don't know a whole lot about how Flatpak packaging works.

Oh, I forgot to update the release version tag for Flatpak (

ProtonUp-Qt/share/metainfo/net.davidotek.pupgui2.appdata.xml

Line 72 in 6b87cab

<release version="2.9.0" date="2023-12-30">

).
The version is still 2.9.1 even though it is only showing 2.9.0 on Flathub.

ImportError: libQt6Core.so.6: cannot open shared object file: No such file or directory
I didn't check but I assume the Steam Deck just has a vanilla Python installation, since Python is a dependency for Proton and only uses the standard library (it's also a dependency for the Steam Client but I'm not sure outside of Proton how the Client uses Python).
It may be possible to run the python3 -m pupgui2 the way you did, but by pointing to the Flatpak Python3 binary

Yes, also the Flatpak is tailored for the KDE Runtime to save some disk space. I wouldn't expect it to work outside the container as it requires all libraries and dist-packages from the ProtonUp-Qt Flatpak and the KDE Runtime.

---

It seems to be a problem with the specific installation and is probably unrelated to ProtonUp-Qt.

Although it somehow reminds me of #87, but I think it is unrelated.

[sonic2kk]

It would be interesting to know if this issue persists after ProtonUp-Qt v2.9.2 is released.