Skip to content

Window is unclickable after upgrade vertical_tabs_panel layout fails and blocks clicks (Linux/Wayland) #9505

@rogerbertan

Description

@rogerbertan

Pre-submit Checks

Describe the bug

After I upgraded to v0.2026.04.27.15.32.stable_02 on Arch Linux (Hyprland, Wayland), the Warp window stopped reacting to mouse clicks. The cursor still moves and buttons light up when I hover over them, but clicks do nothing. Keyboard shortcuts still work.

In ~/.local/state/warp-terminal/warp.log I see these warnings repeating:

[WARN] Failed to compute position for stack child element. Skipping child.
X: Err("Position not set for "workspace_view:vertical_tabs_panel""),
Y: Err("Position not set for "workspace_view:vertical_tabs_panel"").
[WARN] Dismiss underlay was clicked but no handler was set!

It looks like the vertical tabs panel cannot be placed correctly, but its dismiss layer stays on top of the window and catches all the clicks. That would explain why hover works but clicks don't.

As a workaround, I closed Warp and moved the workspace database aside so Warp could create a new one:

pkill -f /opt/warpdotdev/warp-terminal/warp
cd ~/.local/state/warp-terminal
mv warp.sqlite warp.sqlite.bak
mv warp.sqlite-wal warp.sqlite-wal.bak
mv warp.sqlite-shm warp.sqlite-shm.bak

After that, clicks work again. So it seems the new version does not migrate the old vertical_tabs_panel layout data correctly, and this leaves a layer that blocks the clicks.

To reproduce

  1. Use Warp on the previous stable version with vertical tabs enabled, and close it normally so the layout state is saved.
  2. Upgrade Warp to v0.2026.04.27.15.32.stable_02 (Arch warp-terminal package).
  3. Open Warp again.
  4. Move the mouse over the UI: hover effects work (buttons highlight).
  5. Try to click anywhere in the window: nothing happens. Keyboard shortcuts still work, but the mouse is unusable.
  6. Open ~/.local/state/warp-terminal/warp.log and check the latest entries: the "vertical_tabs_panel" position warnings and the "Dismiss underlay was clicked but no handler was set" message appear repeatedly.

Expected behavior

After upgrading, the Warp window should react to mouse clicks normally. The new version should migrate or reset the old vertical tabs layout data safely, without leaving an invisible layer on top of the window that blocks clicks. Hover and click events should both reach the UI as before the upgrade.

Screenshots, videos, and logs

No response

Operating system (OS)

Linux

Operating system and version

Arch Linux (rolling)

Shell Version

bash 5.3.9

Current Warp version

v0.2026.04.27.15.32.stable_02-1

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:ui-frameworkCore Warp UI framework, rendering, layout, and windowing infrastructure.area:window-tabs-panesWindow, tab, pane, and workspace layout management.bugSomething isn't working.os:linuxLinux-specific behavior, regressions, or requests.ready-to-implementThe issue is ready for implementation work.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions