| Summary: | inform applications if data is still being written when trying to unmount removable device | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Benjamin Schmitz <vortex> |
| Component: | libsolid-hal | Assignee: | Alberto Villa <avilla> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | afiestas, mklapetek, phlogi1 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
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. Setting as a wish with the following objective: Show which applications are using the device so the user can close them. In that case, might be probably closed as a duplicate of https://bugs.kde.org/show_bug.cgi?id=96107 |
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.