I use Zorin OS 18 (with fresh install) and sometimes when I open Nautilus, it gives 'Files' is not responding pop-up. Most of the time even though I select "Force Quit", it doesn't quit.
I used commands like "sudo kill -9 ID" and "sudo pkill -9 nautilus" etc but it's not even killable. (I guess since it's stuck in a system call into the kernel, cannot be interrupted, so the call is in uninterruptible sleep.) The only way is rebooting.
I created a bug report in Gnome Nautilus Gitlab Repo but they told me that GNOME 46.4 is too old for them and is no longer supported.
What should I do? Zorin OS 18 is too new but Gnome version it's based on isn't. Would upgrading the gnome version create problem?
During stucks, I can use other file managers such as Nemo and it's working perfectly fine. But it looks so old-fashioned so I prefer to use fixed Nautilus.
I have the same problem - sometimes Nautilus freezes and I have to force close it, which requires me to log back in. I had this issue with Zorin OS, and now I've been using Debian for a week - I'm still having the same problem (there with GNOME 46, here with GNOME 48). Of course, I have some similar extensions, and I've now disabled all but one or two of them. And I also have the Zorin OS Python Colors extension on Debian - maybe the issue is with reading Nautilus Python extensions.
Yes I already tried that.
Today, the error occured again.
This time it's because of rclone (rsync for cloud) onedrive connection problem.
Other file managers give error message but clicking on one button is enough to use the rest of the functionalities.
Nemo does not even throw error unless I open OneDrive folder. (which should be the expected and the best case)
Note: I use a startup script to connect to OneDrive:
sh -c "rclone --vfs-cache-mode writes mount onedrive: ~/OneDrive"
Back to the main question, can I upgrade nautilus version?
Or will be there Zorin OS 18.1 with a more robust file manager/version than Nautilus 46?
Developers of Nautilus refuse to help for v46.4.
Onedrive connection problem doesn't happen so often. So when it happens it's problem of onedrive. But the issue is it's blocking all nautilus, not just that folder. That's a serious bug, other file managers don't have this problem.
Yesterday I tried to make nemo as default but unfortunately it had even more problems especially Bookmarks (like in the screenshot, it's mixing bookmarks with home folders and sometimes it doesn't show home/). I switched back to nautilus. Instead of a launch-at-startup script, I created a script file that launches OneDrive.
(Unfortunately GNOME developers also removed the ability to run a script from nautilus via double clicking.)
I think, You have to make it executable before. To do that, make a Right-Click on the Script, click on Properties and on the Properties Site is at the bottom a Toggle, You have to activate to make it run as a Program.
I used chmod +x ~/bin/OneDrive. But it doesn't become executable by click. Only with terminal or right click -> run as a program.
But I created a desktop item/entry opt
pn to be able to set as default opener.
Also one of the other problems (off-topic) Linux File Managers have is none of them is able to "Show Recent Folders". They only can show recent files.
Actually Browser File Chooser (not nautilus) had this option, but GNOME developers also removed this feature. But they forgot to remove shortcut to show it, at least it's still possible to see recent directories by clicking on Alt R on Gtk File Chooser. I heard that they changed the file chooser on GNOME 47 but I haven't able to try it yet.
Yes, they have. Until this Nautilus and the File Picker were seperate Programs. So, even when the File Picker looked similar to Nautilus, it wasn't Nautilus. With Gnome 47, they have changed that.
You might be right, even though my OneDrive is disabled I got the "Files" is not responding error again. I'm removing both python3-nautilus and ~/.local/share/nautilus-python/extensions/ directory to make sure.
