Summary: | Visually disable eject button when device is busy. | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Dotan Cohen <kde-2011.08> |
Component: | widget-devicenotifier | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | wishlist | CC: | adaptee, meyerm, wilderkde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dotan Cohen
2010-01-14 22:52:57 UTC
It is not possible to know if a device is busy or not without trying to unmount it. I am planning to make this possible in some specific cases (e.g. if a kio job involves the device), but a general solution is not available I'm afraid. On the Debian mailing list it was suggested that (fuser -mv /$mnt_point) would work across distros, and that using lsof when available would be a bit more complete. I probably did not explain myself properly; of course you could /check/ with fuser if the device is busy (even if sometimes it doesn't quite work), but I fear we can't use it in this situation since we would need to poll the device every so often -which is not really desirable- and this could (possibly) prevent devices to go to sleep and such... > we would need to poll the device
> every so often
Not every so often, just when the user opens the Device Notifier plasmoid. I think that's reasonable.
Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable. Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham |