Lex Berezhny 4d847859f5 gpui_linux: Fix Wayland activation requests (#64058)
Closes #59397

Wayland activation requests previously shared a single pending-action
slot. Concurrent requests could overwrite that slot, leaving an issued
token unused and Mutter's global launch indicator active until its
timeout.

Each activation token now carries its own pending window, URI, or path
action. This prevents requests from overwriting one another and removes
the resulting unpaired-token error.

Track the latest eligible keyboard or pointer press together with the
surface that received it. Window activation uses that context when
available; without it, it still requests a token for the target surface
so the compositor can indicate that the window wants attention. URI/path
opens use the input context when available and otherwise retain the
tokenless fallback. Launcher-provided startup token handling remains
unchanged.

The approach builds on the investigation and prototype attached to
#59397, but does not combine serials from unrelated Wayland protocols.

Test results:

- `cargo fmt --all -- --check`: passed after formatting the follow-up
changes.
- `cargo test -p gpui_linux --lib`: 50 passed.
- `cargo build -p zed`: passed.
- `./script/clippy -p gpui_linux`: passed (release, all
targets/features, warnings denied). The wrapper skipped its later
optional checks because `cargo-shear` is not installed.
- Current-head (`412dc7f6f6`) cold-start smoke test under isolated
headless Mutter 51.0 with `WAYLAND_DEBUG=client`: two startup activation
requests, two returned tokens, both tokens passed to `activate`, and 37
surface buffer attachments. No unpaired-token error appeared. Startup
intentionally issues activation requests now.
- Earlier manual GNOME testing covered the original implementation,
before the attention-preserving follow-up. A visual GNOME busy-cursor
check, launcher-provided-token launch, new-window shortcut, and
URL-opening retest of the current head remain outstanding; the headless
startup trace does not cover those interactions.

Release Notes:

- Fixed the global busy cursor lingering after Zed opens on GNOME
Wayland.
- [GPUI] Fixed concurrent Wayland activation requests losing their
pending actions and improved keyboard-triggered activation context
tracking.

---------

Co-authored-by: Anthony <hello@anthonyeid.me>
2026-10-28 16:14:18 +00:00
2026-10-26 13:46:57 +00:00
…
2026-10-26 11:20:07 +00:00
2026-10-26 11:20:07 +00:00
…
…
2026-10-28 14:31:37 +00:00
…
2026-10-26 10:10:32 +00:00
…
…
…
…
…

Zed

Zed CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.


Installation

On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).

Other platforms are not yet available:

Developing Zed

Contributing

See CONTRIBUTING.md for ways you can contribute to Zed.

Also... we're hiring! Check out our jobs page for open roles.

Licensing

Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.

License information for third party dependencies must be correctly provided for CI to pass.

We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:

  • Is it showing a no license specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

Sponsorship

Zed is developed by Zed Industries, Inc., a for-profit company.

If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.

S
Description
No description provided
Readme 1.7 GiB
Languages
Rust 95.4%
JSON-with-Comments 2.4%
Python 0.8%
Inno Setup 0.3%
Tree-sitter Query 0.3%
Other 0.4%