Linux: starting the game with Play leaves no new hookshot_log.txt #2330

Closed

opened 2026-11-11 15:09:55 +00:00 by mooki000 · 0 comments

mooki000 commented

2026-11-11 15:09:55 +00:00

(Migrated from github.com)

Hookshot version

main 49f75dc8, built from source (the cause came in with #2024)

What kind of problem

Something else

What happened

A Linux player who starts the game with Play (in the Builder after a build, or in the launcher that the Hookshot menu entry and hookshot in the game folder open) gets no new hookshot_log.txt. The game writes its log into #2024's capture instead, which keeps the first 64 KiB in hookshot_startup.log once the game has closed and throws the rest away. So the log every issue asks for is missing, or an older run's log is still there and gets sent in its place.

Expected: hookshot_log.txt of this run, with hookshot_log.1.txt to .4.txt kept, as before #2024.

The cause: play-diagnostics.sh gives the game a pipe as its stderr. The game opens hookshot_log.txt only when its stderr is nowhere to log, and a pipe counts as someone reading its output.

Where in the game

Starting the game with Play in the Linux Builder or launcher

How often

Every time

Graphics card and driver version

RTX 4090, NVIDIA 615.78.08 (the code involved does not touch the GPU)

CPU, RAM and operating system

i9-13900K, 93 GB, Arch Linux

Changes from the defaults

None

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

There is none: that is the fault.

Claim

I'm working on this: #2279 is open with the fix and its test. It follows up #2022 and #2024, whose startup capture it keeps. By docs/workflow.md: S3 (1) x reach (Linux players who start with Play; every report from them comes without its log) x confidence 1.0 (cause found, fix tested). I can test on Linux with an RTX 4090 (NVIDIA 615.78.08) and an Intel UHD 770 (Mesa 26.2.5), not on Windows or AMD.

### Hookshot version main 49f75dc8, built from source (the cause came in with #2024) ### What kind of problem Something else ### What happened A Linux player who starts the game with **Play** (in the Builder after a build, or in the launcher that the Hookshot menu entry and `hookshot` in the game folder open) gets no new `hookshot_log.txt`. The game writes its log into #2024's capture instead, which keeps the first 64 KiB in `hookshot_startup.log` once the game has closed and throws the rest away. So the log every issue asks for is missing, or an older run's log is still there and gets sent in its place. Expected: `hookshot_log.txt` of this run, with `hookshot_log.1.txt` to `.4.txt` kept, as before #2024. The cause: `play-diagnostics.sh` gives the game a pipe as its stderr. The game opens `hookshot_log.txt` only when its stderr is nowhere to log, and a pipe counts as someone reading its output. ### Where in the game Starting the game with Play in the Linux Builder or launcher ### How often Every time ### Graphics card and driver version RTX 4090, NVIDIA 615.78.08 (the code involved does not touch the GPU) ### CPU, RAM and operating system i9-13900K, 93 GB, Arch Linux ### Changes from the defaults None ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt There is none: that is the fault. ### Claim I'm working on this: #2279 is open with the fix and its test. It follows up #2022 and #2024, whose startup capture it keeps. By `docs/workflow.md`: S3 (1) x reach (Linux players who start with Play; every report from them comes without its log) x confidence 1.0 (cause found, fix tested). I can test on Linux with an RTX 4090 (NVIDIA 615.78.08) and an Intel UHD 770 (Mesa 26.2.5), not on Windows or AMD.

Commenting is not possible because the repository is archived.