pyfa-org
Previous version of Pyfa crash on Linux during app startup
Bug Report
On the linux AppImage release, if it's a previous version (i.e. not the latest release), pyfa tries to create a network process using webkit at /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0. It errors saying it doesn't exist, even though it's there in the AppImage at /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0
Expected behavior:
The pyfa release pyfa-v2.60.2-linux.AppImage (previous version) should be able to open without crashing.
Actual behavior:
Opening pyfa in terminal results in the following error:
ERROR **: 12:21:58.052: Unable to spawn a new child process: Failed to spawn child process “/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitNetworkProcess” (No such file or directory)
Trace/breakpoint trap (core dumped)
The app then crashes and closes.
Detailed steps to reproduce:
Run a previous version of pyfa AppImage rather than the latest version.
Operating system and version (eg: Windows 10, OS X 10.9, OS X 10.11, Ubuntu 16.10):
Linux Mint 22 Cinnamon
Other information
It might be worth noting that I also see warnings before this error:
Please specify which version. v2.60.2 or v2.61.0dev1 - Singularity 2024-11-09.
Looks like it's trying to spawn "pyfa update available" window and fails.
@DarkFenX It was the pyfa-v2.60.2-linux version that this happened on, and only after there was an update available like you mentioned.
Will take some time to deebug and fix it. Disable update notification / update manually as a temporary workaround.
I had this same issue, and yes, I had to remove the update checking as well. I just leave it off now. Kubuntu 24.04.
Reopen if https://github.com/pyfa-org/Pyfa/releases/tag/v2.61.2 doesn't work
FWIW, I don't believe this is related to the wxPython upgrade as it has been in several previous versions long before the wxPython version change.
For example? v2.61.0 was the first build with wxpython 4.2.2
I'm pretty confident the issue was as early as 2.59.x as well. I've been experiencing it for a long time, several months, and just worked around it and never filed a report.
For example? v2.61.0 was the first build with wxpython 4.2.2
I've tested every version back from 2.60.0 to 2.58.3 and the hang/crash shows up between 2.59.2 and 2.59.4. I can't test 2.59.3 because of #2633.
I don't see any code that would have changed in between though to cause it, so unless it's an issue with the actual AppImage packaged resource and the new version of WebKit I can't see a reason for it.
It's definitely somewhere in the AppImage system because I just tried native 2.59.4 on Ubuntu 24.04 and the issue isn't reproducible, but the AppImage for all versions since 2.59.4 hang or crash.
This no longer occurs on 2.63.1 even in the AppImage and can likely be closed, thanks so much!