thunar crashed while ejecting usb stick

[David F Muller]

when telling Thunar to eject a USB device a warning message appears to say 'data being written'. Even after the icon has disappeared from the left pane and several minutes have passed (even though I never accessed the device even to read from it, the warning persists. I then remove the device and several minutes later Thunar informs me that the eject has failed/timed-out.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: thunar 1.6.15-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sat Apr 14 07:59:38 2018
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2018-04-11 (2 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: Thunar --daemon
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x55d61251d676: mov 0x18(%rdi),%rax
 PC (0x55d61251d676) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
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
Title: thunar crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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