Description of problem: trying to launch file from the icon on the dash, doesn't launch it. Running nautilus from the command line Version-Release number of selected component (if applicable): $ rpm -qa |grep nautilus gnome-terminal-nautilus-3.54.0-1.fc41.x86_64 nautilus-extensions-47.0-1.fc41.x86_64 nautilus-47.0-1.fc41.x86_64 How reproducible: Everytime Steps to Reproduce: 1. Open a Terminal 2. type `nautilus` and press enter Actual results: ``` $ nautilus ** Message: 08:48:15.878: Connecting to org.freedesktop.Tracker3.Miner.Files MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers Gdk-Message: 08:48:16.824: Error 71 (Protocol error) dispatching to Wayland display. ``` Expected results: nautilus lanches and I can use it. Additional info:
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
2. I updated Fedora from 40 to 41 and that broke. How do I know if it's a packaging issue or an upstream issue?
It works fine here. Gdk-Message: 08:48:16.824: Error 71 (Protocol error) dispatching to Wayland display. indicates this is a display stack issue somehow. Is this a real system or a VM? What's the video adapter? Are you using any third party video drivers? Thanks.
It's real system. I found this thread about the issue https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/3 I'll mark this bug duplicate of the one mentioned there. *** This bug has been marked as a duplicate of bug 2301725 ***