GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

[Gunnar Hjalmarsson]

$ dpkg-query -W gnome-shell-extension-prefs
gnome-shell-extension-prefs 42~beta-1ubuntu3
$ gnome-extensions-app
Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

Caveat: I currently have a mix of packages from jammy-release and jammy-proposed.

[Gunnar Hjalmarsson (gunnarhj)]

I couldn't reproduce this in a more clean jammy installation in a VM, so it may be "just me". Please feel free to close it if you can't easily reproduce.

[Daniel van Vugt (vanvugt)]

Seems to be working in both Wayland and Xorg sessions here.

Although I must say it wasn't working for me for a couple of days last week, around the time this bug was created.

[Daniel van Vugt (vanvugt)]

I am seeing this bug again when I build gnome-shell manually.

[Gunnar Hjalmarsson (gunnarhj)]

FWIW: On the installation where have the issue, this is what it looks like in a Xorg session:

$ gnome-extensions-app
Segmentation fault (core dumped)

Same as bug #1966221 in other words. (The command shown in the bug description was run in a Wayland session.)

[Daniel van Vugt (vanvugt)]

Timo, was it bug 1966221 that you meant to assign to mesa?

Regardless, I think we should keep a gnome-shell task here just to make the bug easier to find, and avoid duplicates.

[Daniel van Vugt (vanvugt)]

Maybe related?

https://gitlab.gnome.org/GNOME/mutter/-/issues/2155 which is fixed in 42.rc:
https://gitlab.gnome.org/GNOME/mutter/-/commit/690b8806d

[Gunnar Hjalmarsson (gunnarhj)]

I installed version 42.0-1ubuntu1 of the mutter and gnome-shell packages. Didn't help, neither on Wayland nor Xorg.

[Daniel van Vugt (vanvugt)]

We should probably only discuss Wayland here. Xorg has bug 1966221.

[Gunnar Hjalmarsson (gunnarhj)]

I see a similar error message when trying to start yelp:

$ yelp
Gdk-Message: 01:23:31.232: Error flushing display: Protocol error
$ gnome-extensions-app
Gdk-Message: 01:23:48.075: Error reading events from display: Protocol error

[Daniel van Vugt (vanvugt)]

So this is GTK only? GTK4 only?

[Daniel van Vugt (vanvugt)]

Maybe related to https://gitlab.gnome.org/GNOME/mutter/-/issues/2083 (bug 1967448) ?

[hackel (hackel)]

I don't know if this is helpful, but I had the org.gnome.Extensions flatpak installed, and it starts just fine under Wayland/nvidia. Only when I tried to switch to the deb did I get this error.

[ManOnTheMoon (manonthemoon)]

Having the same error message"error reading events from display: Protocol error" when running wayland. However, extension manager having no issue opening in x11. Ubuntu 22.04 with Nividia driver 510

[Islam (islam)]

This is also happening for me When I launch extension-manager or cheese apps:

[3254489.563] [e-mail]_id([3254489.568] [e-mail](nil, 7, "failed to import supplied dmabufs: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a ")
42)
Gdk-Message: 12:22:58.093: Error flushing display: Protocol error

[DuckDuckWhale (duckduckwhale)]

Also affected (bug 1975647). Notably, this happened after I attempted to dual boot Debian 11 (stable, then testing). The workspace indicator extension worked before then, but disappeared after I switched back.

user@host:~$ gnome-extensions-app
Gdk-Message: 20:03:19.701: Error flushing display: Protocol error
user@host:~$ cheese

(cheese:32950): Gdk-WARNING **: 20:04:45.134: Native Windows taller than 65535 pixels are not supported
Gdk-Message: 20:04:46.246: Error 71 (Protocol error) dispatching to Wayland display.
user@host:~$

In syslog:

gnome-shell[2051]: WL: error in client communication (pid 32877)
cheese[32877]: Error reading events from display: Protocol error

[pakaoraki (pakaoraki)]

I report also this bug, which seams to be related to nvidia on Wayland.

I made few test on my hybrid graphic laptop (Dell xps with GTX1050 Ti ):

- Fresh Ubuntu install on Wayland (no nvidia driver): OK.
- With Nvidia 510 driver, on-demand profile set, login Xorg: OK.
- With Nvidia 510 driver, on-demand profile set, login with Wayland: FAILED. I got this error:

Gdk-Message: 12:20:26.270: Error 71 (Protocol error) dispatching to Wayland display.
I got similar result also with Nvidia profile set instead of on-demand.

- With Nvidia 510 driver, INTEL profile set, login with Wayland: OK.

With Flatpak app (NVIDIA/Wayland):
- Install gnome-extensions with flatpak run org.gnome.Extensions:

The app start BUT you I can’t access to the extensions settings. The sub-windows can’t open, I got this in logs when I press “setting” button of an listed extension:

Sender gnome-shell, WL: error in client communication (pid 16887)
Sender: gjs ,Error reading events from display: Protocol error
Sender gnome-shell, Window manager warning: Ping serial 2322697 was reused for window W118, previous use was for window W111.

-I also test another similar app on flatpak call com.mattjakeman.ExtensionManager:
The app start but when trying to open extensions settings, the sub-windows does not open and I got this logs too:

Sender: gjs, Error flushing display: Protocol error
Sender gnome-shell, WL: error in client communication (pid 17125)

[DuckDuckWhale (duckduckwhale)]

OBS is also affected. Log:

$ obs
...
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
...
info: [pipewire] screencast session created
The Wayland connection experienced a fatal error: Protocol error
Aborted (core dumped)
$

[Daniel van Vugt (vanvugt)]

If the OBS issue is related to this then it will be in some common component like a library or the shell. We don't need to add a task for each app. This problem is too low level for apps to have any control over it.

[Benjamin Birchman (bbirchman)]

Yes same issue. Can confirm pakaoraki's findings.
Razerblade 15 with rtx2060, nivida 510 drivers.

[Daniel van Vugt (vanvugt)]

Looks like Nvidia's egl-wayland is the main suspect:
https://github.com/NVIDIA/egl-wayland/issues/41

[DuckDuckWhale (duckduckwhale)]

Prepending __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json gnome-extensions to affected commands is a workaround (as mentioned in the issue).

[DuckDuckWhale (duckduckwhale)]

Looks like the bug is fixed in 1.1.10 and what's needed is just an update.

[Daniel van Vugt (vanvugt)]

Added a jammy task because most people will understand that better than rls-jj-incoming. This is something I'd like to do in bugs more often, but if it's wrong (@vorlon?) then let me know.