Bug 204201 - inform applications if data is still being written when trying to unmount removable device
Summary: inform applications if data is still being written when trying to unmount rem...
Status: RESOLVED DUPLICATE of bug 96107
Alias: None
Product: solid
Classification: Unmaintained
Component: libsolid-hal (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Alberto Villa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-17 20:43 UTC by Benjamin Schmitz
Modified: 2013-03-05 19:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Schmitz 2009-08-17 20:43:27 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Unlisted Binary Package

If a removable device cannot be unmounted instantly because there is data still being written to it from the cache, solid should report this to applications so that users can be presented with a "please wait" notification (like Gnome does, for example).

At present, if you try to unmount a removable device and flushing the cache takes longer than a certain timeout (30 seconds, I think) solid will show a generic error message ("DBus error: did not receive a reply"). It does not give any reason why the device cannot be unmounted.
Comment 1 Martin Klapetek 2011-12-02 14:15:23 UTC
Bug 212166 was marked as a dependency on this. While it is partially correct, the 212166 does not occur anymore for some time, so it was fixed without this blocker. However I'm adding the comment here for future reference, should this ever get implemented.
Comment 2 Alex Fiestas 2013-03-03 15:17:41 UTC
Setting as a wish with the following objective:
Show which applications are using the device so the user can close them.
Comment 3 Martin Klapetek 2013-03-03 16:12:29 UTC
In that case, might be probably closed as a duplicate of https://bugs.kde.org/show_bug.cgi?id=96107
Comment 4 Alex Fiestas 2013-03-05 19:12:22 UTC
Done, thanks for the feedback !

*** This bug has been marked as a duplicate of bug 96107 ***