RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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

This has already been fixed upstream, see:
https://gitlab.gnome.org/GNOME/gvfs/commit/38831e4ea149a0b4731d123c63d8b493d30ad0be
https://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 (GNOME bug fix and enhancement update), 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/RHBA-2020:3987