nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()

[Lutsenko Danil]

Daily build ubuntu (Ubuntu Disco Dingo, image downloaded 20/01/19), installed without proprietary software.

Version of nautilus is 3.30.4-1ubuntu1.

Following list describes steps for reproduce bug:
1) Install and start new system.
2) Crash should happens on the first start of nautilus (Files app).

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.30.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 20 22:27:57 2019
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2019-01-20 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x55f831f3d119 <nautilus_view_get_selection+9>: mov (%rbx),%rdi
 PC (0x55f831f3d119) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_view_get_selection ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_nautilus:

[Apport retracing service (apport)]

StacktraceTop:
 NAUTILUS_VIEW_GET_IFACE (ptr=0x0) at ../src/nautilus-view.h:40
 nautilus_view_get_selection (view=0x0) at ../src/nautilus-view.c:256
 selection_changed_cb (view=0x0, bar=0x55f83372c380) at ../src/nautilus-view.h:40
 ?? ()
 ?? ()

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.