nautilus crash on search

[Fusion]

Ubuntu 22.04 LTS (updated from 21.10)
nautilus 1.42.1.1-0ubuntu
15.15.0-37-generic
flatpak installed
Type=x11

Expected to happen:
1. open nautilus
2. type anything in search box in any folder (remote or not, empty or not)
3. nautilus do the search.

What happens:
1. open nautilus
2. type anything in search box in any folder (remote or not, empty or not)
3. nautilus crashes and prompt to end the process

What I've tested:
1. sudo apt install --reinstall nautilus
2. rm ~/.config/nautilus
none worked

Strange result:
sometimes (same search, same folder) it doesn't crash. After waiting about 1min (!) doing nothing, the search results appear. After this happy long time, if I try other searches without closing the window, they work as expected.

I would have posted this a week earlier, but then the strange result first came out. So I thought that I could figure it out, but I couldn't. Before that I didn't realize how important the search box was. Now I have installed nemo as I was waiting nautilus to be fixed. If I could test anything that it could help, I would love to help!

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Sebastien Bacher (seb128)]

could you also add the screenshot with an ascii filename, launchpad has a bug which makes it error out when trying to filenames with non ascii encoding

[Fusion (bornolbers)]

In var/crash, there is no nautilus crash. There are 3 files. One named: _usr_bin_gnome-shell.1000.crash, another: _usr_bin_gnome-shell.1000.upload and another: _usr_bin_gnome-shell.1000.uploaded.

On the step two, I manage to find these links which are nautilus crashes

https://errors.ubuntu.com/oops/0654573a-d3bb-11ec-a529-fa163ef35206

https://errors.ubuntu.com/oops/098c138c-d2a5-11ec-a51f-fa163ef35206

I don't understand your second comment. Please guide me in a more simple way if you please. Where can I find this ascii filename? The only thing I could say (if it is not irrelevant to your1 comment) is that the issue doesn't include any file or it's encoding. It is about the nautilus search box. When I try to write to any folder eg. 123 or test.. on "tes" nautilus is already stop responding.

[Sebastien Bacher (seb128)]

thanks. The filename of the screenshot you attached to the bug is 'Στιγμιότυπο στις 2022-06-14 12-11-43.png', ascii would mean using 'a to z' characters

[Fusion (bornolbers)]

The screenshot is the same file as the non-ascii one.
About photo: After two letters searched, it stops responding (as is shown on the screenshot) and it poped up a message says "Force quit" or "Wait" (I am not sure how it truly is in English, I translate it)

[Sebastien Bacher (seb128)]

those error match bug #1726129 but could you maybe try to follow https://wiki.ubuntu.com/Backtrace and get a stacktrace using gdb?

[Launchpad Janitor (janitor)]

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

[Fusion (bornolbers)]

I found where the problem is! After all these months.. There where also two other issues on my new ubuntu 22.10 installation (same as 22.04).
1. SSD M2 temperature was climbing too high.
2. RAM after a few hours of work was also getting full (16gb total) without doing anything special.
3. the issue above with the search that never completes or totally crashes nautilus.

All these are solved at once with this command: "tracker3 reset -s -r"
I noticed that this "tracker-miner-fs-3" app is getting after a while all the amount of the RAM and about a 50% of the cpu.. Also, after I run the command, the search results appears immediately, nautilus start responding again, temperature drops. But as I work, I may have to do it again after a while.
So for about a month now, I was testing it and this command is like the holy grail. Whenever anything in my pc is not responding as usual, I run this command and immediately everything is getting back to normal.
I also noticed that the problem begins if tracker-miner-fs-3 got over 150mb of ram.. then it spreads and issues begin.
Although for the search, it happens in any search. Tested results:
1. open nautilus
2. type a search
3. waiting (if just wait, nautilus will crash) So, I open terminal
4. type this command on terminal "tracker3 reset -s -r"
5. search result immediately find results!

[Josh Finkler (jfinkler1969)]

this bug was driving me crazy, was making my nautilus files folder crash on a regular basis when attempting the simplest search on a brand new install, also seemed to happen when switching between displaying and not displaying hidden files, tried Fusion (bornolbers)'s "tracker3 reset -s -r" solution in post #9 and it worked immediately, haven't been able to replicate the problem for several days of use now, thanks Fusion (bornolbers), you saved 22.10/nautilus for me!