QTads is a cross-platform, multimedia interpreter for TADS games. It is fully compatible with HTML TADS (aka “Multimedia TADS.”) It runs on Linux, macOS and Microsoft Windows.
UNDO buffer sizes have been increased, allowing for more UNDO steps.
Quitting a game while its waiting for a keypress (like a MORE prompt) should not longer result in the next loaded game skipping past its first such “wait for keypess” prompt.
(Linux) The QTads AppImage is now based on Ubuntu 18.04 and will no longer
work on Linux distros older than that.
(Linux) The QTads AppImage no longer requires libfuse to be installed.
To be fair, I was searching for hours trying to figure out how to get this library installed on my laptop, but couldn’t find anything that worked, so I’ll happily welcome the 10 Mbyte.
qt.network.ssl: Incompatible version of OpenSSL (built with OpenSSL 1.x, runtime version is >= 3.x)
I’m guessing that means I’ll be building this from source, then…? Only an intermediate-skill Linux user; sorry if the question seems dumb. Would be far from the first program I had to build from source, so it wouldn’t be an issue. Just making sure that building from source won’t require libfuse to be on my system is all.
That’s not due to the static AppImage loader. That barely has an impact. The reason for the larger size is that libicudata (contains Unicode conversion tables and related static data) is now included in the AppImage. That lib is 25MB (the AppImage is compressed so the final increase is about 10MB.) This is a consequence of upgrading the build system to Ubuntu 18.04 from 16.04.
And are not using any LD_LIBRARY_PATH environment variable shenanigans?
What happens if you extract the AppImage:
./QTads.AppImage --appimage-extract
Then in the resulting squashfs-root directory, edit the AppRun file and replace everything with:
#! /bin/sh
HERE="$(dirname "$(readlink -f "${0}")")"
# try to make Qt apps more "native looking" on Gtk-based desktops, if possible
# see https://github.com/AppImage/AppImageKit/issues/977#issue-462374883
case "${XDG_CURRENT_DESKTOP}" in
*GNOME*|*gnome*|*XFCE*)
export QT_QPA_PLATFORMTHEME=gtk2
;;
esac
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH":"${HERE}/usr/openssl"
echo "$LD_LIBRARY_PATH"
file "${HERE}/usr/openssl"
exec "${HERE}/usr/bin/qtads" "$@"
What does it print when you run it with ./squashfs-root/AppRun?
Entirely my fault. After poking around some linux forums over the years while trying to find solutions, I noticed people often censor their usernames and such, and I guess I absorbed the habit without realizing.
The full output with the full paths are the following:
But I’m stumped. If you launch the appimage itself, you get the error. If you extract it and manually launch AppRun, there’s no error. I assume there’s also no error if you just extract the appimage without modifying AppRun and launch that?
jessica@jesstop:~/Desktop/TextAdventures/QTads$ ./squashfs-root/AppRun
qt.network.ssl: Incompatible version of OpenSSL (built with OpenSSL 1.x, runtime version is >= 3.x)
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed
File looks like this, after removing the part you provided:
#! /bin/sh
HERE="$(dirname "$(readlink -f "${0}")")"
# try to make Qt apps more "native looking" on Gtk-based desktops, if possible
# see https://github.com/AppImage/AppImageKit/issues/977#issue-462374883
# If a system provided openssl library cannot be found, or is not 1.1.x, use the bundled one.
case "$(openssl version -v)" in
'OpenSSL 1.1.'*)
true
;;
*)
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH":"${HERE}/usr/openssl"
;;
esac
exec "${HERE}/usr/bin/qtads" "$@"
