SUMMARY When copying and pasting a file from Dolphin to the desktop by right clicking on the desktop and selecting "Paste One File" does not produce a notification that the operation failed if the file is too large. This causes the user to be unaware that the operation was unsuccessful and the reason for the failure. STEPS TO REPRODUCE 1. Copy a large file which exceeds the free space of the drive to the clipboard. This can be completed with either Ctrl+C or right clicking the file and select copy 2. Right click the desktop and select "Paste One File" OBSERVED RESULT The file is not copied and there is no notification that the paste operation failed. EXPECTED RESULT A notification stating that there is not enough space on the disk to write the file. This notification is shown when pasting within Dolphin. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.1 Kernel KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION
Oof.
Created attachment 155652 [details] Notification when copying fails
Please ignore my attachment i falsely understood the bug. The notification appears when copying folders but the bug is about copying a big enough file
*** Bug 464840 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1646
Git commit 3a750b7ffff5537d06559ddd98eebb9fc14f35d3 by Nate Graham, on behalf of Thenujan Sandramohan. Committed on 04/08/2023 at 15:34. Pushed by ngraham into branch 'master'. Show a notification when attempting to paste a folder/file to desktop failed Example scenario disk full. Before this merge request, copying would fail silently. Related: bug 464840 FIXED-IN: 6.0 M +4 -1 containments/desktop/plugins/folder/foldermodel.cpp https://invent.kde.org/plasma/plasma-desktop/-/commit/3a750b7ffff5537d06559ddd98eebb9fc14f35d3
Thenujan, is there anything else left to do here, or is this bug fully fixed by that commit?
(In reply to Nate Graham from comment #7) > Thenujan, is there anything else left to do here, or is this bug fully fixed > by that commit? It is fully fixed.