File manager stuck when entering file path

I upgraded my softwares to latest version, but the file manager always stuck when I entering file path at its top.

The output of journalctl --follow is as follows:

Mar 28 12:44:28 fedora kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception on GPC 0: WIDTH CT Violation. Coordinates: (0x1b8, 0x8)
Mar 28 12:44:28 fedora kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x500420=0x80000010 0x500434=0x801b8 0x500438=0x1800 0x50043c=0x0
Mar 28 12:44:28 fedora kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception on GPC 1: WIDTH CT Violation. Coordinates: (0x1b8, 0x0)
Mar 28 12:44:28 fedora kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x508420=0x80000010 0x508434=0x1b8 0x508438=0x1800 0x50843c=0x0
Mar 28 12:44:28 fedora kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception on GPC 2: WIDTH CT Violation. Coordinates: (0x1b8, 0x10)
Mar 28 12:44:28 fedora kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ESR 0x510420=0x80000010 0x510434=0x1001b8 0x510438=0x1800 0x51043c=0x0
Mar 28 12:44:28 fedora kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=3518, name=nautilus, Graphics Exception: ChID 0010, Class 0000c997, Offset 00000000, Data 00000000
Mar 28 12:44:31 fedora nautilus[3518]: vkWaitForFences(): The logical or physical device has been lost. (VK_ERROR_DEVICE_LOST) (-4)
Mar 28 12:44:32 fedora nautilus[3518]: vkWaitForFences(): The logical or physical device has been lost. (VK_ERROR_DEVICE_LOST) (-4)
Mar 28 12:44:32 fedora nautilus[3518]: vkWaitForFences(): The logical or physical device has been lost. (VK_ERROR_DEVICE_LOST) (-4)
Mar 28 12:44:33 fedora nautilus[3518]: vkWaitForFences(): The logical or physical device has been lost. (VK_ERROR_DEVICE_LOST) (-4)
Mar 28 12:44:33 fedora gnome-shell[2422]: meta_wayland_buffer_process_damage: assertion 'buffer->resource' failed
Mar 28 12:44:34 fedora gnome-shell[2422]: meta_wayland_buffer_process_damage: assertion 'buffer->resource' failed

How can I fix this? Any help will be appreciated.

Hi! If you’re using a second monitor with an NVIDIA GPU, it might be related to this post:

It seems to be a GTK bug. You may want to report details to GTK GitLab tracker #7441.

3 Likes

running it like that

GSK_RENDERER='gl' gnome-text-editor

solves the issue :slight_smile:

1 Like

GNOME introduced new graphics renderers with GNOME 46 and then again with GNOME 47, which causes such graphics issues with gtk4 apps.

You could add the env. variable to /etc/environment to make it persistent.

3 Likes

I’ve reported this issue (link1), and there are several solutions provided under the similar issue (link2), which is reported by
liviu.

Thank you Saki chan.

1 Like