nautilus crashed while changing directory in top bar

[Christians]

Nautilus crashes while clicking on the top address-bar to change into a subdirectory.

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: nautilus 1:45~rc-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 6 17:29:11 2024
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1693222156
InstallationDate: Installed on 2023-06-06 (274 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
JournalErrors: -- No entries --
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcCwd: /home/christian
SegvAnalysis:
 Segfault happened at: 0x7f1f6b45ac39 <g_type_check_instance_is_fundamentally_a+9>: mov (%rdi),%rax
 PC (0x7f1f6b45ac39) ok
 source "(%rdi)" (0x4bd00000001) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: Upgraded to mantic on 2023-10-14 (144 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

usr_lib_nautilus:
 file-roller 43.0-1
 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
 nautilus-image-converter 0.4.0-2
 python3-nautilus 4.0-1build1

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1813171, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.