nautilus crashed with SIGSEGV in update_dbus_opened_locations()

[Thomas Boerner]

Sorry I don't know how it happened, this report was created "automatically"...

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Sun Apr 5 19:59:02 2020
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2020-01-17 (79 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcCmdline: nautilus --version
SegvAnalysis:
 Segfault happened at: 0x7f7a54cff144: mov 0x20(%rdi),%rax
 PC (0x7f7a54cff144) ok
 source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 update_dbus_opened_locations ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations()
UpgradeStatus: Upgraded to focal on 2020-01-18 (78 days ago)
UserGroups: libvirt vboxusers wireshark
separator:

usr_lib_nautilus:

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