SUMMARY When launching via CLI certain flatpak apps based on GTK (Bottles and Video Trimmer, at least) I receive the following error: `Gdk-Message: 19:45:49.119: Error 71 (Protocol error) dispatching to Wayland display.` If launched through start menu it just fails silently STEPS TO REPRODUCE 1. Install Bottles flatpak through any means (for instance: Discover) 2. Try to launch it using `flatpak run com.usebottles.bottles` OBSERVED RESULT It fails with: `Gdk-Message: 19:45:49.119: Error 71 (Protocol error) dispatching to Wayland display.` EXPECTED RESULT It launches SOFTWARE/OS VERSIONS Operating System: Nobara Linux 40 (Based on Fedora KDE 40) KDE Plasma Version: 6.2.2 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.2 Kernel Version: 6.11.3-200.fsync.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 8845HS w/ Radeon 780M Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon Graphics (I have actually two graphics procesors on Optimus Mode, the other one being NVIDIA GeForce RTX 4060 Max-Q / Mobile) ADDITIONAL INFORMATION Using the flatpak permissions system setting and restricting those apps to not use the Wayland Windowing System socket allows them to launch and work succesfully
Sounds like a bug in the app itself.
(In reply to Nate Graham from comment #1) > Sounds like a bug in the app itself. It may be! However this doesn't happened a few updates back and it's happening on two different apps. Maybe it's on the GTK Flatpak runtime?
Can't reproduce here. Could you attach the full log here? Ideally with the app launched with WAYLAND_DEBUG=1 set?
Created attachment 175348 [details] Log for the bottles error with WAYLAND_DEBUG=1
(In reply to Zamundaaa from comment #3) > Can't reproduce here. Could you attach the full log here? Ideally with the > app launched with WAYLAND_DEBUG=1 set? I've attached the requested log to the issue. The command was `WAYLAND_DEBUG=1 flatpak run com.usebottles.bottles &> bottles-wayland-bug.txt` Thanks a lot for your time!
Ah > wl_display#1.error(wp_linux_drm_syncobj_manager_v1#62, 0, "surface already exists") This is a bug in the NVidia driver, see https://gitlab.freedesktop.org/mesa/mesa/-/issues/11723 (I haven't found an NVidia issue about this, but they're aware of this)