Nautilus file manager crashed on solus 4.7

kemalmao19

hello, i am a new user here.
i really love and enjoy all things here, but sadly the file manager immediately crashed out when i open a folder. i dont have any clue for this. thanks for help.

solus 4.7 gnome

alfisya

Try launching it from terminal and see if there is interesting output (you can copy the output here). Type nautilus in the terminal and press enter.

kemalmao19

alfisya here's the error

** Message: 04:22:13.392: Connecting to org.freedesktop.Tracker3.Miner.Files
GSConnect: [Errno 2] No translation file found for domain: 'org.gnome.Shell.Extensions.GSConnect'
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
MESA-INTEL: warning: ../src/intel/vulkan_hasvk/anv_formats.c:752: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan_hasvk/anv_formats.c:783: FINISHME: support more multi-planar formats with DRM modifiers

(org.gnome.Nautilus:4020): nautilus-file-CRITICAL **: 04:22:16.265: nautilus_file_get: assertion 'G_IS_FILE (location)' failed

(org.gnome.Nautilus:4020): nautilus-file-CRITICAL **: 04:22:16.265: nautilus_file_get_location: assertion 'NAUTILUS_IS_FILE (file)' failed

(org.gnome.Nautilus:4020): GLib-GIO-CRITICAL **: 04:22:16.265: g_file_equal: assertion 'G_IS_FILE (file2)' failed

(org.gnome.Nautilus:4020): nautilus-file-CRITICAL **: 04:22:16.265: nautilus_file_get: assertion 'G_IS_FILE (location)' failed

(org.gnome.Nautilus:4020): nautilus-file-CRITICAL **: 04:22:16.265: nautilus_file_is_gone: assertion 'NAUTILUS_IS_FILE (file)' failed
sys:1: Warning: invalid (NULL) pointer instance
sys:1: Warning: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(org.gnome.Nautilus:4020): GLib-GIO-CRITICAL **: 04:22:16.266: g_file_is_native: assertion 'G_IS_FILE (file)' failed

(org.gnome.Nautilus:4020): GLib-GIO-CRITICAL **: 04:22:16.266: g_file_is_native: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(org.gnome.Nautilus:4020): GLib-GIO-CRITICAL **: 04:22:16.266: g_file_equal: assertion 'G_IS_FILE (file2)' failed

(org.gnome.Nautilus:4020): nautilus-file-CRITICAL **: 04:22:16.266: nautilus_file_is_not_yet_confirmed: assertion 'NAUTILUS_IS_FILE (file)' failed
**
nautilus-file:ERROR:../src/nautilus-file.c:7391:nautilus_file_is_in_trash: assertion failed: (NAUTILUS_IS_FILE (file))
Bail out! nautilus-file:ERROR:../src/nautilus-file.c:7391:nautilus_file_is_in_trash: assertion failed: (NAUTILUS_IS_FILE (file))
Aborted (core dumped)

trinajstica

Maybe you have something unreadable in your trash. Empty your trash can. Maybe you have something unreadable in your folder you want access...?

TraceyC

I see at the end of the output that Nautilus crashed (core dumped). This happens for one of two reasons:

There's a packaging requirement that wasn't met.
That's not the problem here. I'm able to launch Nautilus on GNOME normally.
There's a programming issue.
This is something that we can't fix. You'll need to report this to the Nautilus maintainers. See the app page - Give feedback

Good luck.

alfisya

There are two (closed) bug report I found that might to your interest:

It says the bug can be workaround by copying a content of a random text file and then opening nautilus. If it doesn't solve it, best chance (as TraceyC said) to report it on Gnome nautilus repo.

eryvile

Happens here as well, but only on my laptop (t480s) 😲, my desktop continues to work just fine. Both machines are up to date, so I'll need to dig into the differences in the setup of these two.

As far as I can tell, the issue started to appear with the update to Gnome 48, but I could be wrong on that one.
My workaround is using Nemo for now (which works acutally really well 👍️).

eryvile

Ok, played around a bit with the issues as file dialogs were also crashing. Turns out, the problem was mainly in front of the computer 🤦:
I have Nautilus configured to open objects with a single click. For whatever reason (probably being used to it from my work computer that runs MacOS), I always double clicked on the folder icons, which then led to the crash. Seems like there's some kind of race condition where the second click is evaluated before the action of opening the folder is finished but after it was triggered...

@kemalmao19: maybe that's the issue for you as well? What happens if you single click a folder?

gozo

Guys, what is this about: "Connecting to org.freedesktop.Tracker3.Miner.Files"?

trinajstica

gozo

It's tracker thing (search files)... if you have problem with this, you can reset db with "localsearch reset -s", create new index with "localsearch index", etc...