ASPL ConsoleMissing downloads or failed checksums
These recovery steps describe Console 0.8.0, verified with separately installed ASPL 0.7.0. Check Download status before obtaining files; an unavailable entry has no verified archive to install.
If the archive or Console SHA256SUMS is missing, malformed or fails verification, stop before extraction or execution. Obtain both original files from the same selected release directory again and follow checksum verification. ASPL has its own checksum list. Keep failed files unused if the problem remains; do not bypass the check or substitute an older release. Offline verification needs the separately retained checksum list too.
The window does not open or text is unreadable
Launch the executable from a Linux terminal to read its exact loader or Qt/platform diagnostic. Check the host prerequisites, including external system Qt, platform plugins and their libraries. ASPL's host requirements do not establish Console compatibility. Correct the named host dependency before relaunching.
If a helper, private library, resource or translation is missing, restore the complete matching installation layout. Keep the executable, helpers, private runtimes and shared data together when relocating; copying only the executable breaks that layout. Follow extract and launch with a verified archive. In-window input Retry cannot repair a failure before the GUI opens or install missing libraries.
If the window opens but Arabic or Latin characters are missing, install a system font with the required coverage and review font selection. A saved font name does not prove the font is installed. Console bundles no font.
ASPL is missing, unusable or incompatible
Install ASPL separately and check that the executable you intend to select reports 0.7.0, using tool selection. Console checks launch --aspl, the saved executable and inherited PATH in that order. An invalid override or saved choice fails without fallback; changing PATH alone does not repair it.
Correct the saved field or clear it to use PATH. A launch override remains active until you relaunch without it or with a corrected path. Relative tool paths use the original physical launch directory, independently of Console cd; use an absolute path when diagnosing selection. Settings validates a regular executable, not version compatibility. Read executable Settings and First run launch before trying again. Renaming source does not repair the tool.
Source, data or current-directory paths fail
Check literal path syntax and quote paths containing spaces. Console does not expand ~, $HOME or wildcards. Use -- before an operand beginning with -. Displayed escapes describe native path bytes; they are not syntax to paste back blindly.
For missing or unreadable source, correct the stated path or permissions and select a readable regular target. Symlinks are permitted; Console does not filter filename suffixes. For a deleted or inaccessible current directory, use an accessible absolute cd -- path as described in directory recovery, then inspect pwd and retry explicitly.
If a program cannot find data or TLS files, first set Console's directory to their intended location. An absolute source path does not set the runtime-data directory. Imports follow the canonical source location under the selected tool. Review source and data directories rather than moving files at random.
A filesystem operation fails or remains pending
Read the reported permission, file-type, size or directory-entry limit and follow filesystem limits. cat is for bounded text in a regular file; it is not a binary viewer. A mkdir failure can leave created directories. Inspect the reported count and the filesystem before retrying.
After five seconds, a Still waiting message means the helper remains pending. Ctrl+C requests cancellation; it does not undo effects. The prompt stays read-only until completion or confirmed helper exit. If cancellation or helper death prevents a complete receipt, effects are uncertain and directories may remain. An uninterruptible kernel wait can delay exit indefinitely. Follow cancellation and effects; Console does not roll back or retry automatically.
Editing is paused or Enter does not send text
Check the prompt's owner and phase first. Starting, Sending, Stopping and Finalizing are read-only. Enter confirms active composition before a later Enter submits; an incomplete Local Compose sequence is retained and cancelled first. A paused route also blocks mutation, paste and submission while preserving selection/copy and Settings access.
Read the reported route failure. Prepare the Fcitx route, external IBus daemon and engine or host Local Compose data as applicable. Missing installed helpers require layout repair. Open Settings with Ctrl+Comma, Apply any changed route first, then explicitly Retry input route and return focus to the owning editor. Inspect readiness before typing.
Retry keeps the committed draft and starts fresh input state. It does not replay keys, restore unfinished composition, send retained text or restart a desktop daemon. Unsent input and unfinished composition remain with their original owner. Delivery-unconfirmed input is already submitted and may have reached the program; use sending recovery before another attempt. For shortcuts consumed by temporary controls, check keyboard context.
Settings fail validation or are not saved
If Apply reports an invalid executable, correct or clear that field and Apply again. No preferences change until validation succeeds. Cancel or Escape during validation dismisses the dialog without applying pending choices. Review Apply and Cancel.
A closed dialog does not establish durable saving or input readiness. A save failure leaves live choices usable but unsaved for this window. Correct the reported storage or helper problem, reopen Settings and Apply again. Cancel does not save, and Retry input route does not repair saving. Restore missing helpers using the complete layout. Review saved and window-only Settings; input route, zoom, current directory, history, scrollback and drafts do not survive closure.
Sending or stopping takes longer than expected
After five seconds, Still sending or Still stopping reports pending work, not a completion deadline. Only one submitted line can be pending; repeated Enter queues nothing. Pipe delivery does not prove the program read or acted on input. Ctrl+D requests EOF after pending input drains; it cannot bypass a blocked write or send the current draft. See sending and EOF.
To request termination, dismiss temporary controls and use Ctrl+C in the main view. Stop requests SIGTERM, then SIGKILL after 1,000 ms if needed. Repeating Stop does not restart escalation. An uninterruptible kernel wait can delay exit indefinitely, and descendants outside the process group may survive. Stop and close also waits for completion. Follow Stop and closing.
Keep reading the output and observed outcome. The command prompt returns only after confirmed launch cancellation or observed child exit and finalization. Stop cannot retract delivered input or undo file/network effects. A delivery-unconfirmed record may include partially delivered bytes; inspect effects before explicitly starting another run or resending anything.