Nautilus stopped working overnight

Issues & Assistance
1

Anyone having issues with Nautilus on CachyOS? I was using it last night and today I am receiving the following error:

❯ nautilus

** Message: 10:07:38.128: Connecting to org.freedesktop.Tracker3.Miner.Files
nautilus-application-Message: 10:07:38.130: Failed to initialize display server connection: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.ServiceChannel without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag

(org.gnome.Nautilus:1704): Gtk-WARNING **: 10:07:38.136: Unknown key gtk-button-images in /home/manuel/.config/gtk-4.0/settings.ini

(org.gnome.Nautilus:1704): Gtk-WARNING **: 10:07:38.136: Unknown key gtk-menu-images in /home/manuel/.config/gtk-4.0/settings.ini

(org.gnome.Nautilus:1704): Gtk-WARNING **: 10:07:38.136: Unknown key gtk-modules in /home/manuel/.config/gtk-4.0/settings.ini

(org.gnome.Nautilus:1704): Adwaita-WARNING **: 10:07:38.151: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
MESA-INTEL: warning: ../mesa-24.2.3/src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../mesa-24.2.3/src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers
fish: Job 1, 'nautilus' terminated by signal SIGSEGV (Address boundary error)

I tried restarting, doing an update on pacman, checked online for answers that were recent and reinstalling without any luck. Thoughts?

2

run it with GSK_RENDERER=gl, it seems to be a bug in the NVIDIA driver

See: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/211#note_2576891

3

Just to be clear, I am not using a Nvidia card, just the Intel graphics built onto the chip and I was still having the problem. This did solve the issue though. In Fish, I just set -g -x GSK_RENDERER gl and it worked for me.

4

Then it’s a bug in the wayland protocol. I don’t really have an idea on what’s wrong since the upstream devs don’t quite have a clue either

5

@jayemdaet Just to confirm things, can you show me the output of pacman -Qs | grep nvidia. I want to give the GNOME devs a heads up because at the moment, they are leaning towards this being an NVIDIA driver issue.

FWIW, I can open Nautilus just fine on my AMD+NVIDIA laptop on KDE Plasma.

6

Yep same here KDE Nvidia

 pacman -Qs | grep nvidia
local/lib32-nvidia-utils 560.35.03-3
local/lib32-opencl-nvidia 560.35.03-3
local/libva-nvidia-driver 0.0.12-1.1
local/linux-cachyos-lto-nvidia-open 6.11.0-5
    nvidia open modules of 560.35.03 driver for the linux-cachyos-lto kernel
local/linux-cachyos-nvidia-open 6.11.0-5
    nvidia open modules of 560.35.03 driver for the linux-cachyos kernel
local/nvidia-prime 1.0-5
local/nvidia-settings 560.31.02-1
local/nvidia-utils 560.35.03-4
local/opencl-nvidia 560.35.03-4


 nautilus
** Message: 12:49:30.734: Connecting to org.freedesktop.Tracker3.Miner.Files
nautilus-application-Message: 12:49:30.735: Failed to initialize display server connection: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.ServiceChannel without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag

(org.gnome.Nautilus:204385): Gtk-WARNING **: 12:49:30.747: Unknown key gtk-modules in /home/me/.config/gtk-4.0/settings.ini

(org.gnome.Nautilus:204385): Adwaita-WARNING **: 12:49:30.800: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

(org.gnome.Nautilus:204385): nautilus-tag-manager-WARNING **: 12:49:30.913: Tracker 2 migration: Couldn't run `tinysparql3`: Failed to execute child process “tinysparql3” (No such file or directory)
7

Here is the output for me:

❯ pacman -Qs | grep nvidia

~

I’m using Hyprland on a 12gen Lenovo X1 Carbon laptop. The graphics card shown is:

GPU: Intel Arc Graphics @ 2.25 GHz [Integrated]

8

Thanks. I’ll try to forward it to the GNOME/mesa guys some time soon.

9

@jayemdaet If you can, can you please reply to this issue thread? I think it would be better if you reached out to them instead of me because I am sure there will be back and forth conversations.

Edit:

Can you also provide log of opening nautilus with WAYLAND_DEBUG=1, e.g. WAYLAND_DEBUG=1 nautilus | grep paste-cachyos

10

@naim Should I provide this log with the GSK_RENDERER set to gl or without? Do you want me to provide it here or there?

Thank you for your help! I will check out that thread and reply.

11

i had this error while opening steam

(zenity:118520): Gtk-WARNING **: 01:04:06.321: Theme parser error: gtk-dark.css:4731:21-29: Hash code is not a valid hex color.

thanks to your solution now its working

12

Without the env var.

13

It looks like a different issue than the one I previously mentioned. Nevertheless, it looks like it’s been fixed upstream and a new version will likely release this week. See wayland: Don't call gdk_display_sync() (!7726) · Merge requests · GNOME / gtk · GitLab

14

Thank you for your assistance with this matter! I appreciate your help!

15

P.S. Arch has cherrypicked this and is already in the znver4 repos. If you’re using Zen4 or higher, update the system and the workaround shouldn’t be needed anymore :slight_smile:
Build failed for v3 and v4 repos tho, I’m pushing the admins to do a rebuild.