Nautilus crashes when returning to search results from a directory

[Nibl]

I cannot figure out how to capture the crash. Launching nautilus from terminal does not give any crash logs when it happens and it is very easily reproduced and extremely annoying. To reproduce it yourself, perform the following:

1. Launch nautilus and click on the 'other locations' tab.
2. Select any drive, partition, filesystem, whatever you have there. For the sake of continuity, just select whatever drive Ubuntu is installed on.
3. Type in a search query. It doesn't matter what it is, but it has to return a directory in the results that you can then enter. For example, type 'pictures' into the search to return your pictures folder.
4. Enter any of the directories that show up in the search results. From here, it doesn't matter what you do. As soon as you press back to return to the search results, nautilus will ALWAYS crash.

This obviously makes searching for things like application files, where many directories will have the same name, extremely difficult and cumbersome. I can reproduce this crash 100% of the time. This is on Ubuntu 22.10 with nautilus 1:43.0-1ubuntu1.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 20 20:21:26 2022
InstallationDate: Installed on 2022-07-09 (164 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (60 days ago)
usr_lib_nautilus:
 file-roller 43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
 nautilus-megasync 5.1.0-1.1
 python3-nautilus 4.0-1

[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.

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.

[Nibl (graystripe)]

There is no crash file for it in /var/crash and the whoopsie ID plugged into that URL does not return any recent errors.

Edit: I just crashed Nautilus again in the same manner mentioned above (it's super easy) and no entries appeared. It's not logging them. It's also worth mentioning that I removed all of the extension packages so they're not what's causing it. I've started using Dolphin as my file manager because I really can't deal with not being able to search directories without everything I'm doing in every Nautilus window and tab closing on me.

[Sebastien Bacher (seb128)]

Could you then try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash ?

[Sebastien Bacher (seb128)]

thanks, that indicates it's the same issue than bug #1993127