Description of problem: When ejecting USB storage, thunar's window freezes for some time. It can be moved around but you can't interact with it. It recovers after half a minute or something. If I do `sudo eject /dev/sdd` in terminal the operation is performed immediately. Version-Release number of selected component (if applicable): Thunar 1.6.12 vs XFCE How reproducible: always Steps to Reproduce: 1. mount USB drive 2. umount/eject from thunar Actual results: you need to wait a minute until you can use thunar Expected results: umount immediately Additional info: I tried on 2 computers that I just upgraded from fedora 24 to fedora 26. I followed all necessary steps to remove any outdated packages and everything else appears to be working fine. Moreover no such issues I've seen with Fedora 24. Everything worked instantaneously there.
Or is this gvfs related? https://github.com/linuxmint/Cinnamon/issues/3864#issuecomment-114556598
I think this is a plain thunar-volman issue. When I umount a USB drive I see in xsession-errors: > thunar-volman: Unsupported USB device type "usb". > thunar-volman: Unsupported USB device type "usb-storage". > thunar-volman: Unknown block device type "disk" P.S. When I do `gio mount -e /run/media/avalon/E822-1FC9/` the device is ejected instantaneously.
Found this bug already reported in bug 1469789 Also upstream bug https://bugzilla.xfce.org/show_bug.cgi?id=13729 *** This bug has been marked as a duplicate of bug 1469789 ***
I had this problem, caused by bug 484945. KDE Plasma and Xfce have dbus services with the same name, and Fedora prevents one of them from launching. In my case the xfce4-notifyd service was not running, and that was preventing disk umounting and mouse-wheel speaker volume changes (both of these events want to send a notification, and fail). You can test if a notify service is running with the command: notify-send hello which should result in a small popup with the text, "hello" if it is running. Renaming the service name in /usr/share/dbus-1/services/org.kde.plasma.Notifications.service or just deleting that file altogether fixed it for me after a reboot, or manually invoking the service.