Check prerequisites
Console 0.8.0 targets Linux x86-64 with separately installed ASPL 0.7.0. Use Download for release information online, or the separately retained release record and checksum list offline. The fields below identify the selected archive's checked host requirements.
Release facts are bound to the verified archive and publication receipt. Verify file checksums before installation.
Install ASPL separately using its English installation guide. For offline use, prepare the verified ASPL installation first; the remaining Console steps use local files. Console neither supplies nor installs the compiler. Confirm the selected executable reports ASPL 0.7.0:
"$HOME/.local/bin/aspl" --version
Replace this example executable path with your actual installation. ASPL's independent glibc 2.34 floor does not establish Console's host compatibility. Current Console builds require Qt 6.11 or newer. The observed Qt version below does not prove every newer version works.
| Field | Verified value |
|---|---|
| Verification state | Verified against the selected archive |
| Host baseline | Omarchy 4.0.4 (Arch), Linux 7.2.5-3-omarchy x86-64, Hyprland 0.56.2, XWayland 24.1.13 |
| Qt | 6.11.2 tested, Qt_6.11 symbols required |
| libc | glibc 2.44 tested, bundled ELF requires GLIBC_2.43, no portable host floor |
| Platform plugins | Qt Wayland libqwayland.so, Qt xcb libqxcb.so |
| System libraries | /lib64/ld-linux-x86-64.so.2, libEGL.so.1, libGLX.so.0, libGLdispatch.so.0, libICE.so.6, libOpenGL.so.0, libQt6Core.so.6, libQt6DBus.so.6, libQt6Gui.so.6, libQt6WaylandClient.so.6, libQt6Widgets.so.6, libQt6XcbQpa.so.6, libSM.so.6, libX11-xcb.so.1, libX11.so.6, libXau.so.6, libXdmcp.so.6, libb2.so.1, libbrotlicommon.so.1, libbrotlidec.so.1, libbrotlienc.so.1, libbz2.so.1.0, libc.so.6, libcrypto.so.3, libdbus-1.so.3, libdouble-conversion.so.3, libexpat.so.1, libffi.so.8, libfontconfig.so.1, libfreetype.so.6, libgcc_s.so.1, libglib-2.0.so.0, libgomp.so.1, libgraphite2.so.3, libharfbuzz.so.0, libicudata.so.78, libicui18n.so.78, libicuuc.so.78, libm.so.6, libmd4c.so.0, libpcre2-16.so.0, libpcre2-8.so.0, libpng16.so.16, libstdc++.so.6 (GLIBCXX_3.4.36, CXXABI_1.3.15), libsystemd.so.0, liburing.so.2, libuuid.so.1, libwayland-client.so.0, libwayland-cursor.so.0, libxcb-cursor.so.0, libxcb-icccm.so.4, libxcb-image.so.0, libxcb-keysyms.so.1, libxcb-randr.so.0, libxcb-render-util.so.0, libxcb-render.so.0, libxcb-shape.so.0, libxcb-shm.so.0, libxcb-sync.so.1, libxcb-util.so.1, libxcb-xfixes.so.0, libxcb-xinput.so.0, libxcb-xkb.so.1, libxcb.so.1, libxkbcommon-x11.so.0, libxkbcommon.so.0, libz.so.1, libzstd.so.1 |
| Fonts | JetBrainsMono Nerd Font and Liberation Sans for Latin, Noto Naskh Arabic fallback, external system fonts |
System Qt, its platform plugins and transitive libraries remain external. Install a system font with Arabic and Latin coverage; Console bundles no font. The Fcitx route uses its private runtime without changing desktop profiles. IBus requires a working external desktop daemon and selected engine. Local Compose requires host locale and Compose-table data. Private input workers and their matching libraries must remain in the complete installation.
A missing ELF loader dependency or Qt/platform plugin can prevent the window opening. Repair the host or installation in that case. In-window Retry cannot repair startup failure. If a route pauses after opening, correct the reported resource or endpoint, then explicitly use Retry input route in Settings. Retry retains the committed draft and does not replay keys or restore unfinished composition.
Verify before extracting
Obtain the named Console archive and its Console SHA256SUMS from the same release directory, or use the files and release record retained for offline installation. Compare the archive's SHA-256 with that release record; Download provides it online. ASPL's checksum list belongs to its separate archive. Keep both Console files in a new directory, then run:
sha256sum --check SHA256SUMS
Continue only when the command succeeds and reports aspl-console-0.8.0-linux-x86_64.tar.xz: OK. A missing archive, missing checksum record, malformed list or different digest stops installation. Do not extract or execute it, bypass verification, or substitute an older release. Obtain the original files again; if the problem remains, keep the files unused and return to Download status. An offline archive uses the separately retained checksum list. This generated guide cannot contain the checksum of the archive that encloses it.
Extract and launch
After verification, extract into that new directory. The archive creates a versioned root containing the entire installation:
tar -xJf aspl-console-0.8.0-linux-x86_64.tar.xz
cd aspl-console-0.8.0-linux-x86_64
./bin/aspl-console --version
./bin/aspl-console --aspl "$HOME/.local/bin/aspl"
The reported Console version must match 0.8.0. Console and ASPL have independent versions. The application starts in Arabic. Enter settings or إعدادات, or press Ctrl+, to choose English. Read First run to save a source and send a line of input. Missing helpers fail visibly; moving only the executable cannot produce a working installation.
Keep the complete layout
Keep these directories together when moving or copying the installation. The complete release installation uses these paths:
| Path | Required material |
|---|---|
bin/aspl-console |
Console executable |
libexec/aspl-console/ |
Operation, settings and native-input helpers |
lib/aspl-console/ |
Matching private Fcitx, IBus and Local Compose runtimes and load/resource manifests |
share/aspl-console/ |
Translations, generated guides and resources, install inventory, application source, dependency sources, patches, recipes, licenses and notices |
share/applications/, share/icons/ |
Desktop entry and icon |
share/aspl-console/install-manifest.json records installed files, hashes, modes, build options and ELF dependency edges. Retain original legal and source material unchanged. Private helpers are located relative to the application, not searched on PATH. Keep translations beside the matching layout. The desktop entry can pass a selected .aspl or .لبات file as a draft; it does not make Console the default terminal or source-file handler.
Optional installation and removal
Running from the extracted tree is sufficient. For a stable user location, move the entire versioned root to $HOME/.local/opt/, preserving its internal layout. Example Linux-terminal commands, after checking that the destination does not already exist:
mkdir -p "$HOME/.local/opt"
mv aspl-console-0.8.0-linux-x86_64 "$HOME/.local/opt/"
"$HOME/.local/opt/aspl-console-0.8.0-linux-x86_64/bin/aspl-console" --aspl "$HOME/.local/bin/aspl"
Run these from the directory above the extracted root. Keep any launcher pointed at the executable inside that tree. A file-manager relocation also works. Do not merge a new release into an older tree or copy just its bin directory.
To remove it, close Console, check the versioned directory you intend to delete, and remove that whole Console-owned tree. Remove any launcher you created. Keep separately installed ASPL, source files and program data. Saved Console preferences are separate from the installation; removing the tree does not erase them. A system-wide installation and dependency replacement are maintainer workflows, not prerequisites for this first run.
Select the ASPL tool
Use an absolute executable path with --aspl to make the selection explicit for this launch. Each run checks the launch override, saved executable and inherited PATH in that order. An invalid explicit or saved choice fails without fallback. Settings can validate and save an executable when no override applies; an active launch override remains authoritative and requires a new launch to change it. A save failure leaves live choices window-only.
Relative executable choices and relative or empty PATH entries use the original physical launch directory, independently of later Console cd commands. Use launch options and Settings command for details. A missing tool is repaired by installing ASPL separately or correcting its path, not by changing the source filename.
For startup or integrity failures, use Troubleshooting and its checksum recovery.