# Update wayland-backend to fix Wayland file dialog crash \(\#60621\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/dd68454633ac9fea8b42115ae09568e7395831e2)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: dd68454633ac9fea8b42115ae09568e7395831e2

Requested commit: dd68454633ac9fea8b42115ae09568e7395831e2

Commit: dd68454633ac9fea8b42115ae09568e7395831e2

Tree: d816766d4000e992c20640cc48fb9b04bfad580e

Author: Richard Feldman

Committer: GitHub

## Message

```
Update wayland-backend to fix Wayland file dialog crash (#60621)

On Wayland, closing a window in the brief gap between requesting a
portal file dialog and ashpd exporting the window's surface (used to
parent the dialog) crashed Zed with `Unknown opcode 0 for object
<anonymous>@0`
([ZED-9KB](https://zed-dev.sentry.io/issues/7568720776/)). When the
export request fails because the surface is already dead,
wayland-scanner's generated code silently returns an inert proxy, and
ashpd's `Drop` impl later sends `destroy` on it — which wayland-backend
0.3.11 answers with a panic, because it looks up the request opcode
before checking whether the object is null. wayland-backend 0.3.15 fixes
this
([Smithay/wayland-rs#890](https://github.com/Smithay/wayland-rs/issues/890))
by returning an error instead, which the generated destructor discards,
so the drop becomes a harmless no-op. This bumps the lockfile to 0.3.15
and raises the version floor in `gpui_linux` so the fix can't silently
regress via a fresh lockfile.

Closes FR-100

Release Notes:

- Fixed a crash on Linux (Wayland) when a window was closed just as a
file dialog was being opened.
```

## Parents

- [664b7ecb40b83fa728bc40ef8f0385e35ea01287](https://git.cafe/gitcafe/zed/commit/664b7ecb40b83fa728bc40ef8f0385e35ea01287?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/dd68454633ac9fea8b42115ae09568e7395831e2?format=markdown)