Skip to content

[Bug]: Linux AppImage t3 serve crashes or times out on systemctl stop #40623

Closed

Description

@RibatTRW

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

With the Linux AppImage's desktop-generated t3 launcher installed, use a scratch base directory and a free loopback port:

launcher="$HOME/.t3/bin/t3"
scratch=$(mktemp -d)
systemd-run --user --unit=t3-shim-repro -p TimeoutStopSec=30s \
  "$launcher" serve --host 127.0.0.1 --port 47931 --no-browser --base-dir "$scratch"
# After the test server is ready:
systemctl --user stop t3-shim-repro
journalctl --user -u t3-shim-repro

Repeat with a fresh scratch directory and unit name, adding -p KillMode=mixed to systemd-run.

Expected behavior

The server gets a chance to shut down while the AppImage is still mounted. The launcher releases the mount after the server exits.

Actual behavior

  • Default KillMode=control-group: systemd signals both the server and the AppImage mount helper. The mount goes away during shutdown and the server dumps core with SIGBUS / BUS_ADRERR.
  • KillMode=mixed: systemd signals the launcher's shell first. The launcher waits for the CLI without forwarding SIGTERM. On this machine, stop took 30.2 seconds with a 30-second timeout and systemd sent SIGKILL.

The earlier process-group fix in #24421 starts the mounter in its own session. That session still belongs to the systemd unit's cgroup. With mixed, only the main PID receives the initial SIGTERM.

Impact

Major degradation or frequent failure when stopping this service.

Version or commit

Linux AppImage 0.1.11. The launcher on main at 63fa4c892e still has the relevant signal handling.

Environment

Linux x86_64, kernel 7.2.15-1-omarchy, systemd 262 (262.1-1-arch).

Logs or stack traces

control-group: Process 2790859 (t3code) of user 1000 dumped core.
coredumpctl: Signal: 7 (BUS) si_code: BUS_ADRERR

mixed: State 'stop-sigterm' timed out. Killing.
mixed: Main process exited, code=killed, status=9/KILL
mixed: Failed with result 'timeout'.

Screenshots, recordings, or supporting files

Default stop reproduces SIGBUS

Mixed stop reaches TimeoutStopSec

Terminal recording. Idle gaps are shortened.

05-stop-before-after.mp4

Workaround

Run a separately installed non-AppImage T3 CLI as the systemd unit's executable so it has no FUSE mount dependency.

Prepared by an AI agent on behalf of the account owner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions