Closed spike63995 closed 1 year ago
Just tested on my Steam Deck with ProtonUp-Qt 2.7.4 from Flathub and GE-Proton7-38 installed fine for me. Subsequent launches also work.
Just curious, are you using ProtonUp-Qt AppImage, Flatpak or from source?
Not sure if ProtonUp-Qt logs anywhere but can you run ProtonUp-Qt from terminal and attach the output?
python3 -m pupgui2
~/Applications
- Take note of the filename (maybe something like ProtonUp-Qt-(a lot of letters and numbers).AppImage
) And then from a terminal in that folder, run ./<name of appimage>
net.davidotek.pupgui2
You can take a screenshot of the Terminal output if it all fits on one screen, otherwise you could just copy it into a file and attach that :-)
Yes, the Terminal output of those commands will help diagnose your issue.
You're probably installed ProtonUp-Qt from the Discover app store. If this is the case, open "Konsole", type flatpak run net.davidotek.net
and then press enter.
I maybe should either provide a better guide on how to get this information or make it somehow easier, e.g. adding a right-click option to the .desktop "Run ProtonUp-Qt with Terminal".
Yes, the Terminal output of those commands will help diagnose your issue.
You're probably installed ProtonUp-Qt from the Discover app store. If this is the case, open "Konsole", type
flatpak run net.davidotek.net
and then press enter.I maybe should either provide a better guide on how to get this information or make it somehow easier, e.g. adding a right-click option to the .desktop "Run ProtonUp-Qt with Terminal".
Thanks, I took a screenshot and got a not installed. I included the discover store installation to show you that it should be installed.
EDIT: I don't know if this helps at all, but I tried "flatpak run net.davidotek.pupgui2" and got this:
Loaded ctmod DXVK Loaded ctmod DXVK Async Loaded ctmod DXVK (nightly) qt.pysideplugin: Environment variable PYSIDE_DESIGNER_PLUGINS is not set, bailing out. qt.pysideplugin: No instance of QPyDesignerCustomWidgetCollection was found. Traceback (most recent call last): File "/app/lib/python3.9/site-packages/vdf/init.py", line 131, in parse line += next(fp) StopIteration
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/app/lib/python3.9/site-packages/pupgui2/main.py", line 2, in
SyntaxError: vdf.parse: unexpected EOF (open key quote?) QThread: Destroyed while thread is still running /app/bin/net.davidotek.pupgui2: line 3: 3 Aborted (core dumped) python3 -m pupgui2 "$@" 50,107 Bot
I inputted command "sudo flatpak update --commit=4e6814a479166aba35bc5cb492b3189b32b721fae0a465421df80bfb9b13d48c net.davidotek.pupgui2" and it brought me all the way back to 2.6.0 which makes sense, but it works. So I don't know why the flatpak for the newest version isn't working.
I'm also on the latest stable update on my steam deck.
The issue related to the Flatpak not installed is just a typo :-) As you probably noticed with your second reply.
The log in your second reply is really strange. It seems like the VDF parser for GE-Proton is failing. I can't reproduce this. I tested latest master on my laptop, desktop and Steam Deck, and ProtonUp-Qt Flatpak 2.7.4 on my desktop and Steam Deck. It's really strange that the older release of ProtonUp-Qt is working for you. That to me indicates that it isn't a corrupted download... Unless the older ProtonUp-Qt handles VDF files differently?
Though it would be interesting to see if this works: Go to /home/deck/.local/share/Steam/compatibilitytools.d
and remove the GE-Proton7-29
folder. Then try redownloading with ProtonUp-Qt (either 2.6.0 or the latest, whichever you like).
It'll be interesting to see if the VDF parser is generally failing and it just fell over at GE-Proton7-29 first, or if it's only failing for that one specific GE version.
Unless the older ProtonUp-Qt handles VDF files differently?
The "vdf functionality" (specifically getting the internal tool name) was introduced with v2.7.3.
It'll be interesting to see if the VDF parser is generally failing
It should be working fine... Maybe the vdf file is corrupted or different for this version?
The issue related to the Flatpak not installed is just a typo :-) As you probably noticed with your second reply.
The log in your second reply is really strange. It seems like the VDF parser for GE-Proton is failing. I can't reproduce this. I tested latest master on my laptop, desktop and Steam Deck, and ProtonUp-Qt Flatpak 2.7.4 on my desktop and Steam Deck. It's really strange that the older release of ProtonUp-Qt is working for you. That to me indicates that it isn't a corrupted download... Unless the older ProtonUp-Qt handles VDF files differently?
Though it would be interesting to see if this works: Go to
/home/deck/.local/share/Steam/compatibilitytools.d
and remove theGE-Proton7-29
folder. Then try redownloading with ProtonUp-Qt (either 2.6.0 or the latest, whichever you like).It'll be interesting to see if the VDF parser is generally failing and it just fell over at GE-Proton7-29 first, or if it's only failing for that one specific GE version.
Thanks! This worked perfectly!
Hi,
I had protoup-qt working since I got my steam deck and it never failed. Now today I went to install the latest proton-ge and it wasn't working so I rebooted. When I did so, it just loads the icon at the bottom for a few seconds, then disappears. It's not in the running processes. I tried to uninstall it and reinstall it, same thing. Anyone else having an issue with this?