Bug Report: AppImage fails on Slackware: Missing WebKitNetworkProcess due to hardcoded Debian-style paths
I tried to run the pyfa-v2.62.3-linux.AppImage on Slackware 15.0. The application fails to start due to a missing WebKitNetworkProcess binary, even though webkit2gtk is installed on the system. The AppImage appears to be looking for this binary in a Debian-specific path, which doesn't exist on Slackware. Previous versions worked. It would probably do the same with WebKitWebProcess next. Error Output
** (pyfa.py:23786): ERROR **: 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)
Environment
OS: Slackware 15.0 (x86_64)
WebKit2GTK installed via SlackBuilds:
Actual path: /usr/lib64/webkit2gtk-4.0/WebKitNetworkProcess
AppImage version: pyfa-v2.62.3-linux.AppImage
Steps to Reproduce
-
Install webkit2gtk on Slackware (via SBo)
-
Run the AppImage
-
Observe the fatal error above
Cause The AppImage appears to expect WebKitNetworkProcess at a hardcoded Debian-style path:
/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitNetworkProcess
Slackware (and other distributions) use different directory layouts (e.g., /usr/lib64/...), leading to failure when the binary isn’t bundled.
Expected Behavior The AppImage should either: Bundle WebKitNetworkProcess and related binaries internally, or Use environment variables (e.g. WEBKIT_EXEC_PATH) or relative paths to locate them without relying on host-specific layout
Suggestion To improve portability: Bundle WebKit2GTK components in the AppImage Avoid hardcoded paths specific to Debian-based systems Consider using tools like linuxdeploy and AppImageBuilder to generate self-contained builds
I had the same issue on kde neon and ended installing libwebkit2gtk-4.0-37 package (I had libwebkit2gtk-4.1 which was not working) Fixed the issue
AppImages are typically bundled with everything needed to run on most distributions. I prefer not to modify my system and use AppImages specifically for that reason.
Agreed but in this case it was that or no pyfa. Just saying what worked for me.