+++ This bug was initially created as a clone of Bug #1758237 +++
Description of problem:
When attempting to use the Safely Remove Device, the sync process does not complete though drive is ejected. In addition, a short time after the drive is removed, the warning "Unable to stop drive, Timeout was reached" is shown. User has to restart GNOME-session to get USB drive to appear after re-plugging.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.6
gvfs-1.36.2-1.el7.x86_64
gnome-shell-3.28.3-8.el7_6.x86_64
How reproducible:
Intermittent
Steps to Reproduce:
1.Plug USB drive in
2. Use "Safely Remove Drive" option when right clicking on drive.
3.Wait a few seconds before removing drive.
4. Wait around 20-30 minutes for warning prompt to appear.
Actual results:
Drive ejects but does not complete sync process.
Expected results:
Drive to successfully sync and eject.
--- Additional comment from Ondrej Holy on 2019-10-04 10:53:21 CEST ---
Just a note that I see the following when I try to "Safely Remove Drive" in RHEL 7.6, which is most probably the culprit:
Oct 04 10:25:20 localhost.localdomain gvfs-udisks2-vo[10979]: gvfs_udisks2_drive_stop_finish: assertion 'g_async_result_is_tagged (result, gvfs_udisks2_drive_stop)' failed
Oct 04 10:25:20 localhost.localdomain gvfs-udisks2-vo[10979]: g_dbus_method_invocation_return_gerror: assertion 'error != NULL' failed
Oct 04 10:25:20 localhost.localdomain gvfs-udisks2-vo[10979]: g_error_free: assertion 'error != NULL' failed
Oct 04 10:25:20 localhost.localdomain udisksd[16416]: g_udev_device_get_sysfs_path: assertion 'G_UDEV_IS_DEVICE (device)' failed
Oct 04 10:25:20 localhost.localdomain udisksd[16416]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
--- Additional comment from Ondrej Holy on 2019-10-04 10:54:18 CEST ---
This has already been fixed upstream, see:
https://gitlab.gnome.org/GNOME/gvfs/commit/38831e4ea149a0b4731d123c63d8b493d30ad0behttps://gitlab.gnome.org/GNOME/gvfs/issues/1
However, the fix is not part of any RHEL release yet.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:1766