-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Warp hangs after opening logs view in lazydocker and then exiting #10236
Copy link
Copy link
Open
Labels
area:shell-terminalTerminal input/output, shell integration, prompt behavior, and block rendering.Terminal input/output, shell integration, prompt behavior, and block rendering.area:terminal-inputTerminal command-line input, cursor movement, key handling, and input editing.Terminal command-line input, cursor movement, key handling, and input editing.bugSomething isn't working.Something isn't working.needs-infoMore issue-specific reporter detail is needed before the problem can be confidently triaged.More issue-specific reporter detail is needed before the problem can be confidently triaged.os:macmacOS-specific behavior, regressions, or requests.macOS-specific behavior, regressions, or requests.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.
Description
Metadata
Metadata
Assignees
Labels
area:shell-terminalTerminal input/output, shell integration, prompt behavior, and block rendering.Terminal input/output, shell integration, prompt behavior, and block rendering.area:terminal-inputTerminal command-line input, cursor movement, key handling, and input editing.Terminal command-line input, cursor movement, key handling, and input editing.bugSomething isn't working.Something isn't working.needs-infoMore issue-specific reporter detail is needed before the problem can be confidently triaged.More issue-specific reporter detail is needed before the problem can be confidently triaged.os:macmacOS-specific behavior, regressions, or requests.macOS-specific behavior, regressions, or requests.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.
Summary
Bug: Warp tab becomes unresponsive after entering lazydocker logs view and then attempting to exit.
Problem
When running
lazydockerin Warp and entering the logs view, attempting to exit afterward causes the Warp tab to get stuck. The only reported recovery is closing that tab and starting a new session. The exact key sequence used to exit was not specified.Expected behavior
Exiting from lazydocker/log view should return control to the terminal normally without hanging the Warp tab.
Actual behavior
Warp becomes stuck after viewing logs in lazydocker and attempting to exit. The session cannot be recovered in place and requires closing the tab.
Reproduction steps or desired workflow
lazydocker.Artifacts
None attached.
Warp version
v0.2026.04.29.08.57.stable_01
Operating system
macOS 26.4.1 (build 25E253)