nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

[Nils Büchner]

nautilus crashed while running in background

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42~beta-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 7 12:05:56 2022
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2022-02-15 (19 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcCmdline: /usr/bin/nautilus --gapplication-service
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
 Segfault happened at: 0x7fb7ccd7c9a8 <gtk_widget_get_ancestor+40>: cmp %rax,(%rbx)
 PC (0x7fb7ccd7c9a8) ok
 source "%rax" ok
 destination "(%rbx)" (0x7ffffff00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_widget_get_ancestor () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
UpgradeStatus: Upgraded to jammy on 2022-02-15 (19 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

usr_lib_nautilus:
 evince 41.3-3
 file-roller 3.41.90-1
 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1
 nautilus-share 0.7.3-2ubuntu4

[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 #1962761, 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.