*** This bug is a duplicate of bug 443330 ***
https://bugs.launchpad.net/bugs/443330
Hi Daniel,
I understand what you are saying, however after a discussion with Evan,
I would support the point of view that this is not a usb-creator bug. I
completely agree that using 'safely remove' should not allow any
application to access the device (unmount - yes, safely remove - no).
That said, usb-creator shouldn't have access to safely removed drive
that were safely removed (no application should)> Ah, but it does - why
is that? Let's delve in...
If you believe that a device needs to be physically removed and
reinserted after the 'safely remove' process, then that particular hook
should drop the device out of udev. The 'safely remove' functionality in
gnome does not drop the device out of udev. I suspect gio is the hook
which is guilty of making the device still available to udev and
therefore to usb-creator.
Therefore it's a gnome bug not a usb-creator one where the functionality
of 'safely remove' should be changed. I would request that you report
this bug. Not sure against which package though. I think it may be gvfs
if not gnome-utils or gnome-mount, soryyu... not sure. Hope this helps!
--
usb-creator operates on mounted filesystems, does not display confirmation
dialogs, issue warnings about data loss
https://bugs.launchpad.net/bugs/445810
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
