You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
updated my system a few nights ago and any time i try to launch lutris it immediately crashes
Traceback (most recent call last):
File "/usr/bin/lutris", line 58, in <module>
from lutris.gui.application import Application # pylint: disable=no-name-in-module
ModuleNotFoundError: No module named 'lutris'
The text was updated successfully, but these errors were encountered:
You have updated Python to a newer version and the Lutris package hasn't been updated to that version
You have messed around with pyenv and Lutris is using the wrong python version
I want to find out the root cause of this so we can find ways to prevent it.
Right now, I'm considering a port of Lutris to Qt which would allow us to """""compile""""" the code into a single binary and not depend on the state of the user's Python installation. But if we go that route, this is going to take a very long time to achieve. There might be some workarounds we can find in the mean time.
I put some time into this issue today and ive solved it for me, i hope others with the issue can confirm the fix.
After comparing a fresh OS install on a vm to my non-working lutris install I noticed when i ranwhich python and which python3 the output on my non-working system was the wrong directory.
For me on Manjaro(Arch) the directory for each command should show /usr/bin, to set this correctly you just need to make sure there is no other versions of python overwriting it in local user folders such as /usr/local/bin or /home/user/.local/lib. Some programs like pyenv and conda change these directories automatically.
You should also make sure the lutris module is actually in the right python folder /usr/lib/python3.11/site-packages/lutris
updated my system a few nights ago and any time i try to launch lutris it immediately crashes
The text was updated successfully, but these errors were encountered: