caja crashed with SIGSEGV

[Nathanael C. Higley]

From what I can tell all I did was eject an USB flash drive from caja and shortly later caja crashed.

I'm running ubuntu-mate with the latest updates as of 2018-04-15

Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Arch: amd64

caja:
  Installed: 1.20.2-0ubuntu1
  Candidate: 1.20.2-0ubuntu1
  Version table:
 *** 1.20.2-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: caja 1.20.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Sun Apr 15 17:18:27 2018
ExecutablePath: /usr/bin/caja
InstallationDate: Installed on 2018-04-13 (2 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: caja
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5607c79f2674: cmpl $0x1e,0x4(%rdi)
 PC (0x5607c79f2674) ok
 source "$0x1e" ok
 destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: caja
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: caja crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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