nautilus --version SIGSEGV in g_application_impl_get_dbus_object_path()

[Alexandre Speltri]

Ubuntu 20.04 GNOME, everything updated

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 26 02:02:04 2020
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2020-03-26 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325)
ProcCmdline: nautilus --version
SegvAnalysis:
 Segfault happened at: 0x7f06ef0c7144: mov 0x20(%rdi),%rax
 PC (0x7f06ef0c7144) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

usr_lib_nautilus:

[Apport retracing service (apport)]

StacktraceTop:
 g_application_impl_get_dbus_object_path (impl=0x0) at ../../../gio/gapplicationimpl-dbus.c:855
 g_application_get_dbus_object_path (application=<optimized out>) at ../../../gio/gapplication.c:2129
 update_dbus_opened_locations (self=0x555c73310210) at ../src/nautilus-application.c:1480
 bus_acquired_cb (conn=<optimized out>, name=<optimized out>, user_data=0x555c73d65740) at ../src/nautilus-freedesktop-dbus.c:168
 connection_get_cb (source_object=<optimized out>, res=0x7f06d4007580, user_data=0x555c73d6ea00) at ../../../gio/gdbusnameowning.c:504

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!