Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UMU-LAUNCHER-Debian-Not_Working #385

Closed
kieran1188 opened this issue Feb 15, 2025 · 16 comments · Fixed by #389
Closed

UMU-LAUNCHER-Debian-Not_Working #385

kieran1188 opened this issue Feb 15, 2025 · 16 comments · Fixed by #389

Comments

@kieran1188
Copy link

All following update (1.2.0-1 - 1.2.3-1) are not working and come up with the following error.

@R1kaB3rN R1kaB3rN added the question Further information is requested label Feb 15, 2025
@R1kaB3rN
Copy link
Member

R1kaB3rN commented Feb 15, 2025

Please share that following error in plaintext in your post.

@kieran1188
Copy link
Author

Sorry, New updates are now working. When I logged it the first time, I was being late for work. It came up with an error regarding some Facebook python error, I've come back from work, and I've tried to see if I can get the error again and no issues now.

@R1kaB3rN
Copy link
Member

No problem, and thanks for clarifying.

While it’s hard to say without any sort of log, the Facebook Python error is likely related to the pyzstd module which this project currently builds by default for Debian-based distributions. In your case, the module won’t be available until Debian 13 (trixie), assuming you’re not already on it. For that module though, the libzstd library is a dependency and you’ll need to ensure you have it installed. However, I expect most users to have it installed transitively by some other package as it’s sorta fundamental, and the defacto compression library to use for modern applications.

@R1kaB3rN
Copy link
Member

Closing as resolved. If you ever run into that Python error again, then please reopen the issue.

@kieran1188
Copy link
Author

@R1kaB3rN R1kaB3rN reopened this Feb 16, 2025
@R1kaB3rN
Copy link
Member

You should be able to fix that error by ensuring the zstd library is installed in your system.

@R1kaB3rN
Copy link
Member

R1kaB3rN commented Feb 16, 2025

Should be called libzstd on Debian. If you can confirm that it fixes the problem then I can add it as a required dependency.

@R1kaB3rN R1kaB3rN marked this as a duplicate of #388 Feb 16, 2025
@kieran1188
Copy link
Author

I have libzstd and python3-pyzstd installed and still the error

@kieran1188
Copy link
Author

Last working one was 1.1.4-1 of which I'm using currently

@R1kaB3rN R1kaB3rN added can't reproduce and removed question Further information is requested labels Feb 16, 2025
@R1kaB3rN
Copy link
Member

Sorry, the library should be called libzstd1, not libzstd.

Also, I cannot reproduce this error in a Debain 12 environment created from distrobox.

Steps to reproduce:

  1. Install distrobox
  2. distrobox create -i debian:latest
  3. distrobox enter debian-latest
  4. cd $HOME
  5. sudo dpkg --add-architecture i386
  6. curl -LJO 'https://github.com/Open-Wine-Components/umu-launcher/releases/download/1.2.3/python3-umu-launcher_1.2.3-1_amd64_debian-12.deb'
  7. sudo apt install python3-xxhash python3-cbor2 libzstd1
  8. sudo apt install ./python3-umu-launcher_1.2.3-1_amd64_debian-12.deb
  9. umu-run -h
  10. UMU_LOG=1 GAMEID=umu-0 PROTONPATH=GE-Latest umu-run ""

Terminal output:

📦[foo@debian-latest foo]> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
📦[foo@debian-latest foo]> umu-run -v
umu-launcher version 1.2.3 (3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0])
📦[foo@debian-latest foo]> which umu-run
/usr/bin/umu-run

@kieran1188
Copy link
Author

I'm currently on Trixie with backport, what versions of python etc are you using?

@kieran1188
Copy link
Author

@kieran1188
Copy link
Author

When using the version that works, when I use "umu-run -v" it comes back with the following:

umu-launcher version 1.1.4 (3.13.2 (main, Feb 5 2025, 01:23:35) [GCC 14.2.0])
steamrt is up to date
Traceback (most recent call last):
File "/usr/bin/umu-run", line 8, in
sys.exit(main())
~~~~^^
File "/usr/lib/python3/dist-packages/umu/main.py", line 9, in main
return umu_run()
File "/usr/lib/python3/dist-packages/umu/umu_run.py", line 871, in main
check_env(env, thread_pool)
~~~~~~~~~^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/umu/umu_run.py", line 149, in check_env
raise ValueError(err)
ValueError: Environment variable not set or is empty: GAMEID

@R1kaB3rN
Copy link
Member

When using the version that works, when I use "umu-run -v" it comes back with the following:

Because you’re not using version 1.2.3.

I'm currently on Trixie with backport, what versions of python etc are you using?

The Python version is irrelevant in this issue, and the Debian package we provide is intended and targeted for Debian 12. Nothing more, nothing less.

@GloriousEggroll do we want to support Debian 13, which currently isn’t officially released?

@R1kaB3rN
Copy link
Member

Confirmed that a Debian 13 variant of this package works as expected in my pull request #389 using basically the same above steps, except changing the container variant pulled from distrobox to Debian 13 and downloading the GitHub Debian 13 artifact instead.

@R1kaB3rN
Copy link
Member

R1kaB3rN commented Feb 16, 2025

Closing as completed. Any Debian-related issues that are not Debian 12 or Debian 13 are unsupported and will be automatically closed. Furthermore, you should not run into that ImportError related to the pyzstd module because I've confirmed that all the relevant files are expected to be within the package with the correct permissions and ran the command GAMEID=umu-0 PROTONPATH=GE-Latest umu-run ""

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants