Red Hat Bugzilla – Bug 214364
KDE: 'safely remove' does not safely remove USB devices (pen drives, etc.)
Last modified: 2008-04-25 15:13:54 EDT
KDE "safely remove" is not safe in the sense that some data is lost, specially
in the case one has just copied a large (say, 100 Mb) file to the pen drive.
According to Markku Kolkka, «the problem I have seen is that the device icon on
the KDE desktop changes immediately after "safely remove" to indicate that the
device is unmounted and ready to be removed, but the system is actually still in
the process of writing data to the device. If the device is removed too early,
some files will be missing or the filesystem may be corrupted and there's no way
to know when it's actually safe to remove it.»
This bug may be related to "199128: USB drive icon disappears before write cache
Ah ha, looks very similar indeed, so far we have
fc4: bug #199128: "USB drive icon disappears before write cache"
fc5: bug #194296 "USB drive icon shows as unmounted before write cache flushed"
Does the problem still persist in F8?
*** Bug 218775 has been marked as a duplicate of this bug. ***
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
I cannot test it anymore, as now I do not use KDE.
Thanks, we'll just have to keep an eye out for this.