NEW 280210
[GTK] Unable to start: Error 71 (Protocol error) dispatching to Wayland display
https://bugs.webkit.org/show_bug.cgi?id=280210
Summary [GTK] Unable to start: Error 71 (Protocol error) dispatching to Wayland display
alex.parrill
Reported 2024-09-23 14:22:27 PDT
My webkit2gtk programs and the MiniBrowser example both fail to start on Wayland on my Nvidia desktop. They print the following error and exit: Gdk-Message: 17:14:30.589: Error 71 (Protocol error) dispatching to Wayland display. Running the programs with `WEBKIT_DISABLE_DMABUF_RENDERER=1` fix the issue. Running the program with `WAYLAND_DEBUG=` shows this line at the end: [4192651.933] {Display Queue} wl_display#1.error(wp_linux_drm_syncobj_surface_v1#55, 4, "explicit sync is used, but no acquire point is set") Tested with the v2.46.0 package for Arch Linux, and Nvidia proprietary driver version 560.35.03. Probably related to https://bugs.webkit.org/show_bug.cgi?id=262607 . I'm using webkit2gtk via wry, which tauri also uses, and they have an issue here: https://github.com/tauri-apps/tauri/issues/10702 , so I don't think I'm the only one.
Attachments
alex.parrill
Comment 1 2024-09-23 14:26:37 PDT
Running under X11, either via setting `GDK_BACKEND=x11` or by running an X11 desktop env, also does not work, but has somewhat different symptoms. The webview screen is all white and the application prints the following message: Failed to create GBM buffer of size 1024x730: Invalid argument The underlying page controls still work, but aren't visible. Setting `WEBKIT_DISABLE_DMABUF_RENDERER=1` fixes this issue.
Carlos Garcia Campos
Comment 2 2024-09-24 00:36:20 PDT
What compositor is this? gnome-shell/mutter? What GTK4 version? From WebKit we just render into the gtk widget without using any wayland specific thing.
alex.parrill
Comment 3 2024-09-24 05:57:24 PDT
I've tested this with Gnome 47.0.1 and Plasma 6.1.5; it happens under both. GTK4 version 4.16.1.
Note You need to log in before you can comment on or make changes to this bug.