Bug 445488

Summary: Inconsistent behavior when I try to safely remove a device in use via Disks & Devices applet
Product: [Plasma] plasmashell Reporter: Patrick Silva <bugseforuns>
Component: Disks & Devices widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.23.3   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=445484
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: screen recording

Description Patrick Silva 2021-11-14 14:33:54 UTC
Created attachment 143543 [details]
screen recording

SUMMARY
Please watch the attached screen recording. When I try to remove a device in use for the first time, Disks & Devices applet says 'One or more file on this device are open within an application'. However, if I try to remove the device in use again, removing just fails without any feedback.

EXPECTED RESULT
Disks & Devices applet should always say 'One or more file on this device are open within an application'
when we try remove a device in use

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 1 Nate Graham 2021-11-23 19:07:26 UTC
Cannot reproduce with a file that is actually open on the device. I notice you canceled the transfer in the middle, and presumably the half-transferred file is triggering this message in the moments before it gets cleaned up or something. Is there a .part file left over on the device? Maybe you're just hitting a side effect from Bug 445484...
Comment 2 Patrick Silva 2021-11-23 19:50:42 UTC
(In reply to Nate Graham from comment #1)
Is there a .part file left over on the device? Maybe you're just
> hitting a side effect from Bug 445484...

Yes. This bug seems related to bug 406721.
Comment 3 Nate Graham 2021-11-24 19:16:35 UTC
Cool, let's get that fixed, then.

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