-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
[Bug Report] "ImportError: wx/_core.cpython-312-x86_64-linux-gnu.so: undefined symbol: _Py_NegativeRefcount" #1093
Comments
I have not seen that before. |
Looks like it is part of cpython but only included in certain contexts. |
I have a post open at wxPython to see if someone there can shed some light. |
The most likely issue I can think of is that the prebuilt version of wx you are using is compiled with different flags to the version of Python you are using. It is expecting the symbol from python but it doesn't exist. |
My virtual uses 3.12 so I'm going to grab 3.9 and try again, especially since I found this on the Python 3 changelog:
I'm willing to bet "Python is too new" is the problem with the Flatpak build too. We'll see after the test machines finish. |
Running Amulet in a virtual Python 3.9.19 after installing via pip was a success.
Next, I'll see if I can build the Flatpak using this older version of Python. |
Also, for the record, I found THIS handy little tool, which has made managing different versions of Python extremely easy! |
I have used this before which looks similar |
Can this be closed? |
Go ahead. 👍 |
Bug Report
As part of troubleshooting the flatpak build, I created a brand new VENV for Amulet 0.10.35 and attempted to install it with PIP (which is what the Flatpak builder does), everything was apparently successful. When I attempt to load it, it crashes right out of the box:
Current Behaviour:
Amulet crashes on load - before GUI even presents itself
Expected behavior:
Amulet doesn't crash on load
Steps To Reproduce:
My entire terminal log is available here so you can see exactly what I did and what the result was.
Environment:
Additional context
Attachments
Screenshots
Worlds
The text was updated successfully, but these errors were encountered: