nautilus crashed with SIGSEGV

[Prasanna Loganathar]

Unknown crash

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct 26 13:53:17 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'234'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1376, 742)'
 b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']"
InstallationDate: Installed on 2019-06-23 (124 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7fe5af3ee982: mov 0x380(%rax),%rax
 PC (0x7fe5af3ee982) ok
 source "0x380(%rax)" (0x00000380) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to eoan on 2019-10-24 (1 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo wireshark
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-06-29T23:49:14.971566
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 #1844026, 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.