From f9fd8fa2ab109633503f105faba06aa19e7ffd7c Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Thu, 7 May 2026 15:19:17 -0700 Subject: [PATCH] fix(docs): make Linux tar log-collection commands actually work Closes #16. The Linux tar commands in 'Gathering Warp Logs' fail with 'tar: warp.log*: Cannot stat: No such file or directory' on Linux: bash leaves the unmatched literal 'warp.log*' as the file argument to tar, and tar then looks for a literal file named 'warp.log*' inside the -C directory. Switch to 'cd into the directory first, then tar' so the shell expands the glob in the right pwd. Wrap the cd+tar in subshell parens so the user's pwd is preserved after the command finishes (the cd only affects the subshell). Verified with GNU tar 1.35 + bash: - OLD command reproduces the reporter's failure (exit=2, 'Cannot stat: No such file or directory'). - NEW command exits 0 and archives warp.log, warp.log.1, warp.log.2. - Caller's pwd is unchanged after the subshell exits. (Earlier draft of this fix used GNU tar's --wildcards flag, but --wildcards only enables glob matching during EXTRACTION/listing; in creation mode tar still treats arguments as literal paths. Reverted to the cd-then-tar approach the issue reporter suggested.) Also normalize the indentation in the Linux :::caution RUST_LOG block to the 4-space indent already used by the macOS and Windows tabs. Co-Authored-By: Oz --- .../sending-us-feedback.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx b/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx index c34186c..e2f2b23 100644 --- a/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx +++ b/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx @@ -158,7 +158,7 @@ Warp's logs and crash reports _**do not**_ contain any console input or output. Run the following to zip the Warp logs to your home directory: ```bash - tar -czf ~/warp-logs.tar.gz -C ~/.local/state/warp-terminal warp.log* + (cd ~/.local/state/warp-terminal && tar -czf ~/warp-logs.tar.gz warp.log*) ``` **Warp Preview logs on Linux** @@ -166,19 +166,19 @@ Warp's logs and crash reports _**do not**_ contain any console input or output. Run the following to zip the Warp Preview logs to your home directory: ```bash - tar -czf ~/warp_preview-logs.tar.gz -C ~/.local/state/warp-terminal-preview warp_preview.log* + (cd ~/.local/state/warp-terminal-preview && tar -czf ~/warp_preview-logs.tar.gz warp_preview.log*) ``` :::caution If your issue is graphical (e.g. no display of windows) or a crash, please run Warp with the following command to capture more log information: ```bash -# Run if Warp on Linux is installed + # Run if Warp on Linux is installed RUST_LOG=wgpu_core=info,wgpu_hal=info MESA_DEBUG=1 EGL_LOG_LEVEL=debug warp-terminal - + # Run if Warp Preview on Linux is installed RUST_LOG=wgpu_core=info,wgpu_hal=info MESA_DEBUG=1 EGL_LOG_LEVEL=debug warp-terminal-preview -``` + ``` :::