[bug] Error 71 (Protocol error) dispatching to Wayland display.
Lunasciel opened this issue · 6 comments
Describe the bug
Application won't start anymore.
Error:
Gdk-Message: 23:55:52.007: Error 71 (Protocol error) dispatching to Wayland display.
Reproduction
Execute yarn tauri dev
under Linux and try to start your Application
Expected behavior
Normal starting without errors
Full tauri info
output
> tauri info
[✔] Environment
- OS: Linux Rolling Release X64
✔ webkit2gtk-4.0: 2.44.3
✔ rsvg2: 2.58.3
✔ rustc: 1.80.0 (051478957 2024-07-21)
✔ cargo: 1.80.0 (376290515 2024-07-16)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
- node: 22.6.0
- yarn: 1.22.22
- npm: 10.8.2
[-] Packages
- tauri [RUST]: 1.7.1
- tauri-build [RUST]: 1.5.3
- wry [RUST]: 0.24.10
- tao [RUST]: 0.16.9
- @tauri-apps/api [NPM]: 1.6.0
- @tauri-apps/cli [NPM]: 1.6.0
[-] App
- build-type: bundle
- CSP: unset
- distDir: ../dist
- devPath: http://localhost:1420/
- framework: React
- bundler: Vite
Stack trace
No response
Additional context
I haven't changed anything in the project since the last time and everything still worked.
Looks like the bug has made it's way to GitButler. Getting this exact error trying to start it.
Thought it was this error at first, but the problem persists after removing the window-state file
Edit: this is giving me nvidia-problem vibes. Are you using nvidia?
this is giving me nvidia-problem vibes. Are you using nvidia?
Can confirm on my end that it is related to NVIDIA. I got the same error on my NVIDIA-only machine.
Here is the log with WAYLAND_DEBUG=1
, https://pastebin.pl/view/5fd8b401
[2610755.730] {Display Queue} wl_display#1.error(wp_linux_drm_syncobj_surface_v1#50, 4, "explicit sync is used, but no acquire point is set")
Gdk-Message: 04:05:57.352: Error 71 (Protocol error) dispatching to Wayland display.
Edit: My machine is running Arch Linux, NVIDIA 560.35.03, NVIDIA EGL Wayland 1.1.16.
I recently migrated over to wayland, and came across this same issue (though in a tauri v2 app)
A temporary solution is to use
WEBKIT_DISABLE_DMABUF_RENDERER=1 pnpm tauri dev
This happens for me when running Webkit2gtk's MiniBrowser example app, so it's likely an upstream issue. I've filed https://bugs.webkit.org/show_bug.cgi?id=280210 .
fixed some of the issues causing “Error 71 (Protocol error)” in tauri-apps/tao#979.
I believe the update will be applied in the next version after tao 0.30.2.
is this fixed?