UPDATE: To test whether libnvidia-egl-wayland1 was the ultimate source of this issue, I switched back to the NVIDIA 535 drivers (which usually works correctly) but I also manually installed the libnvidia-egl- wayland1 & libnvidia-egl-wayland1:i386 packages from the Terminal.
After restarting into Wayland, the issue appeared again (just like with the newest NVIDIA 550.107.02 package) so my hypothesis was correct. Launching libadwaita apps failed with the same error messages as I mentioned earlier, and the Settings > About "Graphics" field showed the "NVIDIA" GPU being used (not "Mesa Intel" as it previously did when everything worked correctly): https://i.imgur.com/5MpmGMJ.png As soon as I removed only the libnvidia-egl-wayland1 & libnvidia-egl- wayland1:i386 packages and rebooted, libadwaita apps launched normally again and the Settings > About "Graphics" field showed "Mesa Intel" (instead of "NVIDIA"): https://i.imgur.com/ezCIwOa.png As a result, I can confirm that the presence of libnvidia-egl-wayland1 changes this behaviour (even with the NVIDIA 535 drivers) and causes this issue. After looking through the debian/changelog for the nvidia-graphics- drivers-550 source in jammy, I found that "libnvidia-egl-wayland1" was added as a dependency for "libnvidia-gl-550" in version 550.100-0ubuntu0.22.04.2 of this package. This lines up with my experience testing the system's behaviour with different versions of the NVIDIA 550 drivers. If the maintainer of the nvidia-graphics-drivers-550 source package could remove "libnvidia-egl-wayland1" as a dependency for the "libnvidia-gl-550" package in jammy (as was the case before), this issue should probably be resolved. I believe that's the fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2080282 Title: Apps run on the discrete Nvidia GPU by default instead of the Intel integrated GPU Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've identified a regression with the latest update to the NVIDIA 550 drivers in Ubuntu 22.04. This prevents any libadwaita apps from launching while using the Wayland display server. It appears that the latest available NVIDIA 550.107.02 package pulls in some new dependencies, such as libnvidia-egl-wayland1 and some other i386 support packages (libnvidia-egl-wayland1:i386 libwayland- client0:i386 libffi8:i386). They seem to enable Wayland support out of the box, which sets Wayland as the default desktop for new installations of Ubuntu 22.04 (assuming software updates are enabled from the Ubuntu installer). However, any attempt to launch libadwaita apps from within Wayland with the NVIDIA 550.107.02 drivers installed always fails. When launching any of these libadwaita apps from the Terminal, it always returns one of the following three errors: - Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - Gdk-Message: Error reading events from display: Protocol error - Gdk-Message: Error flushing display: Protocol error Some of the affected apps include gnome-text-editor, gnome-sound-recorder, and gnome-shell-extension-manager which are available from the standard Ubuntu repositories. When I researched these error messages, I found that other Linux distros also seem to be experiencing this bug, including Fedora: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/6 However, the "GSK_RENDERER=gl" solution in bhundven's post in that thread didn't work in Ubuntu 22.04 when I tested it. For reference, I was able to replicate this issue on an ASUS Zenbook UX303LB with an NVIDIA 940M graphics card running the newest available NVIDIA 550.107.02 driver on a fresh installation of Ubuntu 22.04.4 with all of the latest software updates installed. However, downgrading to an older version of the NVIDIA drivers (like version 535) without full Wayland support makes this error disappear, with either Xorg and Wayland selected from the login screen. In our testing, Ubuntu 24.04 doesn't seem to be affected by this issue in Wayland or Xorg. However, we also noticed that Ubuntu 24.04 still defaults to Xorg on NVIDIA 550.107.02, even with the latest updates downloaded by the Ubuntu installer (unlike Ubuntu 22.04). I'm aware that your team is preparing to launch Ubuntu 22.04.5 on 12 September. However, as this is an out-of-the-box bug with the default version of the NVIDIA drivers for most NVIDIA users, it may be worth investigating this issue to avoid new users having a bad experience. Perhaps it might be worth sticking with Xorg by default in Ubuntu 22.04 installations with the NVIDIA 550 drivers as a workaround? If you need any help or additional information when trying to replicate or investigate this issue, please let me know and I would be happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2080282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
