Differences

This shows you the differences between two versions of the page.

--- lanternterminal:installing [2026-11-07 21:48] – Update Lantern Terminal guides for 0.2.1 slaterm
+++ lanternterminal:installing [2026-11-10 13:46] (current) – Update Lantern Terminal guides for 0.5.0 slaterm
@@ Line 1: / Line 1: @@
 ====== Installing Lantern Terminal ======
-Get version 0.2.1 from [[https://retro.theiguru.au/lantern-terminal/|the download page]]. Both platforms are 64-bit.
+Get version 0.5.0 from [[https://retro.theiguru.au/lantern-terminal/|the download page]]. Both platforms are 64-bit.
 ===== Windows =====
-Download ''Lantern-Terminal-0.2.1-windows-x64-setup.exe'' and run it. It installs for your current user under LocalAppData by default and adds a Start menu entry. Start **Lantern Terminal** from that menu.
+Download ''Lantern-Terminal-0.5.0-windows-x64-setup.exe'' and run it. It installs for your current user under LocalAppData by default and adds a Start menu entry. Start **Lantern Terminal** from that menu.
-For a portable installation, download ''Lantern-Terminal-0.2.1-windows-x64.zip'', extract it and run ''LanternTerminal/lantern-terminal.exe''. Keep the extracted DLLs, plugins and data folders with the executable. The package includes Qt, Python and OpenSSH clients; it does not install an SSH server.
+For a portable installation, download ''Lantern-Terminal-0.5.0-windows-x64.zip'', extract it and run ''LanternTerminal/lantern-terminal.exe''. Keep the extracted DLLs, plugins and data folders with the executable. The package includes Qt, Python, libssh (the built-in SSH engine), FreeRDP (Remote Desktop) and OpenSSH clients; it does not install an SSH server.
 The application targets Windows 10 or later. The installer and raw TCP/scripting workflow have passed Wine checks, but physical Windows ConPTY and device/provider behaviour still need target testing.
@@ Line 13: / Line 13: @@
 ===== Linux =====
-On a compatible Debian-based distribution, download ''lantern-terminal_0.2.1_amd64.deb'', open a terminal in that directory and run:
+On a compatible Debian-based distribution, download ''lantern-terminal_0.5.0_amd64.deb'', open a terminal in that directory and run:
 <code bash>
-sudo apt install ./lantern-terminal_0.2.1_amd64.deb
+sudo apt install ./lantern-terminal_0.5.0_amd64.deb
 lantern-terminal
 </code>
@@ Line 26: / Line 26: @@
 ===== Upgrading, configuration and removal =====
-Close the application when your sessions can safely be disconnected, then install the new package. Windows reinstall/uninstall checks verify that existing profiles are preserved. On Linux, remove the package with ''sudo apt remove lantern-terminal''; on Windows, use **Settings → Apps**. Back up your configuration before changing computers or upgrading: **Help → About Lantern Terminal** shows its exact directory.
+From 0.5.0 on, Lantern tells you when a new version is out and **Update Now** installs it (Help → Check for Updates… checks at once). To upgrade by hand, close the application when your sessions can safely be disconnected, then install the new package. Windows reinstall/uninstall checks verify that existing profiles are preserved. On Linux, remove the package with ''sudo apt remove lantern-terminal''; on Windows, use **Settings → Apps**. Back up your configuration before changing computers or upgrading: **Help → About Lantern Terminal** shows its exact directory.
 The Windows portable archive still uses the normal user configuration directory unless launched with ''--config'' pointing elsewhere. To try an independent profile on Linux:
@@ Line 37: / Line 37: @@
   * **Saved session is missing:** clear the Sessions filter, expand the folder, then use **Edit → Go to Session Manager**. Check the profile directory in Help → About if you used ''--config''.
-  * **Unreadable interface or wizard:** install version 0.2.1 and choose **Options → Theme → Light** (or Dark/System). Changes apply immediately.
+  * **Unreadable interface or wizard:** install version 0.3.1 or later and choose **Options → Theme → Light** (or Dark/System). Changes apply immediately.
-  * **SSH reports it could not open a trace logfile:** version 0.2.1 fixes the temporary-file handle conflict on Windows. Upgrade, then reconnect.
+  * **Ctrl+F, Ctrl+Q or Ctrl+N no longer open Find, Exit or New session:** since 0.3.2 these keys go to the terminal. Use Ctrl+Shift+F, Ctrl+Shift+Q and Ctrl+Shift+S, or the menus.
+  * **A session says it is using OpenSSH:** it uses something the built-in SSH engine does not support yet (X11 or agent forwarding, extra OpenSSH options). That is expected; it connects as before.
+  * **SSH reports it could not open a trace logfile:** version 0.3.1 fixes the temporary-file handle conflict on Windows. Upgrade, then reconnect.
   * **Colours need changing:** open **Options → Session properties → Terminal → Appearance**, then use **Choose colour…**. Cancel preserves the previous colour.
   * **No password prompt / Permission denied (publickey):** the server accepts SSH keys only. Select the authorised private key under Session properties → Connection → SSH2 → Private key / identity, or use a key in your SSH agent. A server key accepted at first connection only verifies the server identity.