Extensions settings window do not open in Wayland

[rodrigogonegit]

How did you upgrade to 22.04? (Fresh install / Upgrade)
Upgraded from 21.10. Deleted old extensions. Just the system extensions are installed.

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
gnome-shell

➜  ~ apt policy gnome-shell 
gnome-shell:
  Installed: 42.0-2ubuntu1pop0~1650293247~22.04~acb38ae
  Candidate: 42.0-2ubuntu1pop0~1650293247~22.04~acb38ae
  Version table:
 *** 42.0-2ubuntu1pop0~1650293247~22.04~acb38ae 1001
       1001 http://apt.pop-os.org/release jammy/main amd64 Packages
        100 /var/lib/dpkg/status
     42.0-2ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

Issue/Bug Description:
Attempting to open the settings window of any extension fails.

Relevant journal logs:

Apr 23 02:18:14 pop-os gnome-shell[7094]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Apr 23 02:18:14 pop-os gnome-shell[7094]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Apr 23 02:18:14 pop-os gnome-shell[7094]: meta_window_set_stack_position_no_sync: as
sertion 'window->stack_position >= 0' failed
Apr 23 02:18:14 pop-os gnome-shell[7094]: WL: error in client communication (pid 12968)
Apr 23 02:18:14 pop-os gjs[12968]: Error reading events from display: Protocol error

Steps to reproduce (if you know):

• Open Extension Manager or the gnome extensions website
• Press the settings button
• Nothing happens
• The Extension Manager seems to toggle all the extensions off (but nothing really is disabled)

Expected behavior:
The settings window should open.

Other Notes:
As it might be related to the GPU, I'll leave the driver versions I'm using.

➜  ~ vainfo            
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 ()
vainfo: Supported profile and entrypoints

➜  ~ nvidia-smi
| NVIDIA-SMI 470.86       Driver Version: 470.86       CUDA Version: 11.4     |

[rodrigogonegit]

Update: it only happens on Wayland.

[lfom]

App crashes on Wayland only, workaround: GDK_BACKEND=x11 gnome-extensions-app.

[rodrigogonegit]

App crashes on Wayland only, workaround: GDK_BACKEND=x11 gnome-extensions app.

Thanks but that does not work:

➜  ~ flatpak run --env=GDK_BACKEND=x11 com.mattjakeman.ExtensionManager  

(extension-manager:2): Gtk-WARNING **: 19:23:56.946: cannot open display: 

[lfom]

➜ ~ flatpak run --env=GDK_BACKEND=x11 com.mattjakeman.ExtensionManager

(extension-manager:2): Gtk-WARNING **: 19:23:56.946: cannot open display:

Hmmm, this is not the stock Extensions app (it comes from a deb package), this app is something else available in Flathub, so not related to Pop!_OS. The stock Extensions app (gnome-extensions-app) works fine using the environment variable as explained.

[lfom]

App crashes on Wayland only, workaround: GDK_BACKEND=x11 gnome-extensions-app.

Actually it seems to be a problem between GTK and Nvidia proprietary drivers, it works fine here (Pop 22.04/Wayland on AMD). I can get the app to launch on Nvidia using the command above, but all settings windows crash. No luck changing the renderer either, with or without forcing it to use Xwayland:

GDK_BACKEND=x11 GSK_RENDERED=cairo gnome-extensions-app
GDK_BACKEND=x11 GSK_RENDERED=opengl gnome-extensions-app
GSK_RENDERED=cairo gnome-extensions-app
GSK_RENDERED=opengl gnome-extensions-app

[mmstick]

NVIDIA Wayland isn't supported so if that's the only issue I think we can close this.

[lfom]

Just for the record:

[komorebinator]

Just for the record:

I also have 2 graphics cards, what exactly shall I do to get it working?
I have no idea how the bug is related to nvidia drivers since DE shall render on AMD

[lfom]

I also have 2 graphics cards, what exactly shall I do to get it working? I have no idea how the bug is related to nvidia drivers since DE shall render on AMD

If you have hybrid graphics with AMD, try:

DRI_PRIME=1 gnome-extensions-app

or 0 instead of 1 (to use iGPU).

[komorebinator]

komorebi@komorebi-pc:~$ DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: AMD RENOIR (LLVM 13.0.1, DRM 3.42, 5.15.0-48-generic)

komorebi@komorebi-pc:~$ DRI_PRIME=1 glxinfo | grep "OpenGL"
libGL error: failed to create dri screen
libGL error: failed to load driver: nouveau
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 13.0.1, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.0.5
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5 (Compatibility Profile) Mesa 22.0.5
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

So the first one must be AMD, but both are not working.

komorebi@komorebi-pc:~$ DRI_PRIME=0 gnome-extensions-app
Gdk-Message: 02:45:48.194: Error reading events from display: Protocol error
komorebi@komorebi-pc:~$ DRI_PRIME=1 gnome-extensions-app
Gdk-Message: 02:45:56.602: Error flushing display: Protocol error

This must be an AMD driver issue, hopefully I'll receive some fixes with HWE updates.

Anywy @lfom thank you for help!

[lfom]

@komorebithrowsatable Are you using Wayland with AMD? The command below also fails? If yes, stock Pop installation?

GDK_BACKEND=x11 gnome-extensions-app