[plasmashell] [Bug 416783] Unmounting removable device fails if the progress bar reached 100% but the file transfer was not in fact completed
https://bugs.kde.org/show_bug.cgi?id=416783 oso changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=281270| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416783] Unmounting removable device fails if the progress bar reached 100% but the file transfer was not in fact completed
https://bugs.kde.org/show_bug.cgi?id=416783 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- Looking into it, I don't think there's any local workaround we can add, since there's no way for the applet to distinguish between "in use by the file.so library due to in-progress transfers" and in use by the file.so library due to a transfer that has technically completed but the final contents are still being written to the disk" *** This bug has been marked as a duplicate of bug 281270 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416783] Unmounting removable device fails if the progress bar reached 100% but the file transfer was not in fact completed
https://bugs.kde.org/show_bug.cgi?id=416783 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=281270 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416783] Unmounting removable device fails if the progress bar reached 100% but the file transfer was not in fact completed
https://bugs.kde.org/show_bug.cgi?id=416783 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Summary|Unmounting removable device |Unmounting removable device |fails silently if the |fails if the progress bar |progress bar reached 100% |reached 100% but the file |but the file transfer was |transfer was not in fact |not in fact completed |completed CC||n...@kde.org --- Comment #2 from Nate Graham --- Yeah the root cause is the annoying Bug 281270. Now it no longer fails silently, but it says something like "the device is in use by file.so". Which is technically true but maybe we can present this a bit better. -- You are receiving this mail because: You are watching all bug changes.
