Troubleshooting

Troubleshooting

veetee does not start

• Missing libraries on Linux (libgtk-4.so.1, libadwaita-1.so.0): install GTK 4 and libadwaita, e.g. sudo apt install libgtk-4-1 libadwaita-1-0.
• Blank or black window: veetee needs OpenGL 3.3. On Linux check glxinfo -B (package mesa-utils); inside virtual machines enable 3D acceleration.
• Windows: nothing appears, or "OpenGL unavailable": update the graphics driver. Remote Desktop sessions and some virtual machines only offer OpenGL 1.1.
• Windows: SmartScreen warning: the build is not code-signed yet; choose More info → Run anyway.
• Windows: a missing DLL: keep the bin, lib and share folders of the zip together; veetee.exe cannot be copied out on its own.

Output is slow

A VT420 (the default model) scrolls smoothly at nine lines a second, as the hardware did, and holds the host back meanwhile. Open Set-Up (F3) → Display, choose Jump Scroll, then Save in the Set-Up Directory. On a VT500 model choose Display → Scrolling mode → Jump, then Save settings.

No sound, or too much

• Keys click and the bell beeps by default, as on a DEC terminal. Turn the keyclick and bells down or off in Keyboard Set-Up (F3) and Save.
• veetee uses the default audio output; check that one is set in the desktop's sound settings. Without one, veetee reports "no sound" when it starts and uses the desktop bell.
• Building from source on Linux needs libasound2-dev.

Drawing is slow

Glow, afterglow and the curved screen add a post-processing pass. On a slow or software-only OpenGL (some virtual machines), switch them off under Screen in the window menu.

Serial port: permission denied or busy

• Linux: join the dialout group (sudo usermod -aG dialout $USER) and log in again.
• veetee opens the port exclusively; close other programs such as picocom, minicom, PuTTY or ModemManager that hold it.
• Windows: use the name Device Manager shows under Ports (COM & LPT), e.g. --serial COM3.
• Garbled text usually means a speed or parity mismatch; see Connections.

Flatpak

• "flatpak-spawn: command not found" or a shell that exits at once: the Flatpak runs shells, commands and ssh on the host through the Flatpak portal; check that flatpak-portal and flatpak-session-helper are running (they start with the desktop session).
• Saved connections or Set-Up are missing: the Flatpak keeps its own settings in ~/.var/app/com.issinoho.Veetee/config/veetee; copy files from ~/.config/veetee if you used another package before.
• Serial port not found: the Flatpak can open devices in /dev, but still needs the dialout group membership described above.

Screen readers

The terminal is exposed through AT-SPI as a terminal. If Orca says nothing, check that accessibility is on in the desktop settings and that GTK_A11Y is not set to none.

Keys do not do what the host expects

• On OpenVMS run SET TERMINAL/INQUIRE and check SHOW TERMINAL (see OpenVMS).
• Over SSH that inquiry does nothing: OpenVMS never asks, and leaves the _FTAn: device a VT102. Set /DEVICE_TYPE by hand in LOGIN.COM (OpenVMS).
• Your desktop may take F-keys or Ctrl+Shift shortcuts for itself; check the desktop keyboard shortcuts, or move the binding in the Keyboard Map window.
• The keypad follows the LK401 layout: Num Lock is PF1, keypad / is PF2 (Keyboard).
• If you changed the keymap and want the original back, use Restore Defaults in the Keyboard Map window.

The screen looks wrong

Record the session with a checkpoint (Ctrl+Shift+M) at the wrong screen and open an issue with the file attached:

veetee --record problem.vtrec --telnet vms1

Mention the model (--model), the host and application, and what the real terminal shows. Typed keys are not in the recording, but the host's output is; check it for anything private first.