Recovery and troubleshooting
If the main Logonomic window crashes, continue with the surviving terminals in Soter for Logonomic. If one terminal stops, or Logonomic cannot start or finish closing, use the matching section below.
After the main Logonomic window crashes
Every edition includes Soter for Logonomic. If the main Logonomic window crashes, Soter opens automatically with all your surviving terminals still running. Recovery information appears alongside the terminals.
Recovery cannot restore a program that also terminated, or preserve running work through a power loss or operating-system shutdown. For a conversation whose program has ended, use session resumption.
Work with the recovered terminals
- Find the terminal in the overview, scrolling as needed.
- Check its current output and prompt, particularly if you were sending a command when Logonomic crashed.
- Click inside it and continue working. Scrollback, selection, search, and the program's commands remain available.
Soter for Logonomic is dedicated to recovery. About these terminals explains the recovered sessions. Start new sessions in Logonomic.
Terminal settings apply to the original terminals once they are attached in Soter. Appearance changes are saved and shared across those terminals. Each live terminal keeps its own Copy on selection (this terminal) override.
Close one recovered terminal or leave Soter
| Action | Effect |
|---|---|
| Close terminal | Requests closing that original terminal session. |
| Close the Soter for Logonomic window | Leaves the recovery view; it does not close, restart, or replace the original sessions. |
To stop work, close the relevant terminals deliberately. If Soter remains open and asks you to retry window Close, the departure could not be confirmed. Follow that instruction; the message also states that the original terminals have not been closed.
If recovery is still active and original surviving terminals need a view, Soter opens again automatically after its window closes. Wait for the original terminals to reappear, scrolling to reach them all. Terminals you explicitly closed stay closed. If the view does not return, follow Attachment and connection problems.
Return a recovered terminal to Logonomic
- Reopen Logonomic.
- Find the retained live session in Sessions and select Show.
- Select Return terminal to workspace on its terminal tab.
The original running terminal moves back into Logonomic with its existing session. Once it is attached in Logonomic, that window's saved terminal defaults apply; the live terminal's Copy on selection override is preserved. If Return is unavailable, read its tooltip and allow any connection or move in progress to finish. You can continue in Soter while resolving a reported problem. Do not close and replace the terminal to return it: that would end the original session.
For a terminal you deliberately opened in its own Logonomic window, follow Separate terminal windows.
Attachment and connection problems
If Soter says This terminal could not be attached. Trying again automatically. or Terminal attachment was not confirmed. Trying again automatically., allow it to retry. Use Retry terminal connection when offered to reconnect to the original terminal.
| Problem | What to do |
|---|---|
| A terminal reports lost connection | Read the adjacent status and use an offered retry. The connection error alone does not establish that its program ended. |
| Mouse input is off in … retained terminal(s) | Check the affected terminals; keyboard input and other terminals may still work. |
| Input delivery interrupted | Inspect the program's output before repeating a command that may already have run. |
| Saved terminal/task status could not be reconciled, but live status remains available | Continue in the live terminals and include the message in a support report. |
| Surviving terminals never appear, or a fresh shell appears in their place | Report the missing recovery, including terminal names, the visible message, and whether separate windows still work. Starting replacement launchers does not restore the originals. |
When one terminal stops or cannot start
Read the terminal's last output and detailed status before restarting it.
| Symptom | What to check |
|---|---|
| Launch fails immediately | Runner, executable, launcher script, working directory, and the reported error. |
| CLI asks to sign in or reports an account error | The CLI's authentication and the launcher's selected account. |
| Needs you | The program's question or permission request. |
| Quiet or Unknown | Check the prompt. A quiet screen does not establish that work finished. |
| Error or Failed | The detailed message and last output. Resolve the command or account error before trying again. |
| Close and remember is unavailable | Hover for the reason; the session needs a confirmed supported resumable conversation. |
| Logonomic Free refuses a new terminal | Close an unneeded terminal and wait for shutdown to release its slot. |
After a terminal ends, Resume this conversation reopens its exact supported conversation. Start a new terminal session runs the launcher again without restoring the previous command state. See Stop, close, restart, or resume.
Normal application close
Save or resolve open text edits, merge changes, and failed launcher saves before closing Logonomic. These can hold the window open so you can finish the work. Once closing proceeds, Logonomic normally shuts down its running terminals. Supported conversations remain in history under the usual retention policy.
Separate terminal windows can keep running after the main window closes. Close them too if you intend to stop all terminal work. Returning one to the workspace requires a connected main window. Closing Soter after a crash has the different effect described above.
Startup failures
Read the startup message and support code, then select Copy details to save the diagnostic text for a report. Closing the startup window dismisses that attempt. Follow the code you received; these are not steps to try in order.
Another instance or startup attempt exists
| Support code | Response |
|---|---|
| STARTUP-INSTANCE-001 | Logonomic is already open in this Windows session. Bring the identified instance forward or close it normally. |
| STARTUP-INSTANCE-002 | Another startup or shutdown is still active, or an existing instance is unresponsive. Wait for an active operation to finish; report the exact detail if it remains stuck. |
Check the identified instance before ending processes: separate terminals may still contain live work.
Background session startup
| Support code | Response |
|---|---|
| STARTUP-SESSION-003 | Startup timed out. Let intensive system work settle, then try again. Keep the details if it repeats. |
| STARTUP-SESSION-004 | A required log or executable could not be opened. The detail identifies which; check profile access and installation files. |
| STARTUP-SESSION-005 | A required part of startup failed. Use the accompanying detail when reporting it. |
| STARTUP-SESSION-006 | Application components are incompatible. Safely close the relevant instance and reopen from one complete installation; repair mixed or incomplete files. |
See Getting started to identify the active installation and profile. Copying one executable into a different installation is not a complete repair. Do not delete a profile or its history as routine startup troubleshooting.
Startup window, interface, and graphics
| Support code | Response |
|---|---|
| STARTUP-SPLASH-001 | A startup component is missing or blocked. Check the named file and repair the installation if needed. |
| STARTUP-SPLASH-002 | The startup window stopped communicating. Close the attempt and reopen; report a repeat with copied details. |
| STARTUP-GRAPHICS-001 | Graphics initialization or display failed. Reopen Logonomic; if it persists, restart the computer and check the graphics driver. |
| STARTUP-PRESENTATION-001 | The main window took too long to appear. Let intensive system work finish and reopen. |
| STARTUP-PRESENTATION-002 | The main window could not finish opening. Reopen and report a repeat with details. |
| STARTUP-UI-001 | The interface could not load. Check for an incomplete or mismatched installation and repair it. |
| STARTUP-SERVICES-001 | Required services did not start. Restart Logonomic and report the details if it repeats. |
Shutdown needs attention
After you request a normal close, Logonomic shutdown recovery can appear if cleanup needs more time or help. Finishing shutdown means work is progressing; Shutdown needs your attention asks you to act. This window concerns the close you requested; crash recovery takes place in Soter.
Check Affected processes and sessions, elapsed time, and the activity log. Show details expands the underlying failure. A termination request is not confirmation that a process stopped: look for Termination failed, Still running after deadline, or The process has not been confirmed stopped.
Available actions
| Action | Use |
|---|---|
| Continue waiting | Allow more time for the existing shutdown. |
| Retry termination | Try again to stop the identified processes and sessions. |
| Try as administrator… | On Windows, address an access-denied failure when this option is offered. Respond to the operating system's elevation prompt. |
| Show details / Hide details | Inspect or collapse the failure detail. |
Cancelling an administrator prompt leaves the shutdown result unresolved; check the updated status. Terminal session results … not yet saved means final records still need saving, even if the programs have exited. Let shutdown finish both stopping programs and saving results. Do not delete protected profile state or session history to bypass it.
If the shutdown window loses contact
Shutdown recovery lost contact means the window cannot confirm cleanup. Its actions become unavailable. Follow the displayed instruction to reopen Logonomic and restore the live shutdown screen. No shutdown recovery is active means there is no active operation to display.
Appearance, navigation, and input problems
| Symptom | First useful action |
|---|---|
| Text is missing, distorted, or overlaps | Try Glyph only and a known monospace font in Terminal settings; check Cell width and display scaling. |
| Cell width does not look right | Check Cell width, font and display scaling. See Cell width and effective font size. |
| Ctrl+click does not open a terminal hyperlink | Check the supported links and system application; a printed URL may need to be selected and copied. |
| Ctrl+C copies instead of interrupting | Copying clears the selection; a new Ctrl+C reaches the program. |
| Right-click inserts text | Right-click is paste unless the terminal program handles it. Check your clipboard. |
| The wheel scrolls the wrong area | Use the terminal scrollbar for output or Alt+wheel for the overview. |
| A terminal is absent from overview | Check separate windows, the plain-terminal filter, and Sessions for ended work. |
| Esc does not leave overview full screen | Use F11 or the full-screen exit control. |
| The desktop terminal has a narrow grid | If Companion controls sizing, select Reclaim terminal sizing for this desktop tab. |
| Return is disabled in a separate window | Read its tooltip for a disconnected workspace, active close/move, or unavailable terminal. |
See Terminals for full procedures and Logonomic Companion for phone connection problems.
Prepare a useful support report
Include the exact error and support code, plus:
- Logonomic edition and version, installed or portable distribution, and operating system.
- The action immediately before the problem and its approximate time.
- What stopped: the main window, one terminal, or input/display only.
- For a crash, whether Soter opened, whether all surviving terminals were reachable by scrolling, and whether they accepted input.
- Copied startup/shutdown details and the result of any retry.
- For launcher problems, the runner and executable; for drawing problems, the font, display scaling, monitor arrangement, and graphics-driver information.
Use Copy details on a startup error and the copyable version/build information in Terminal settings. Review logs and screenshots for credentials and private work before sharing them.