| Summary: | Selection broken after shift-deleting files, potential risk of data loss | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Christian (Fuchs) <kde> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | efeciftci, john.kizer, kfm-devel |
| Priority: | NOR | ||
| Version First Reported In: | 25.04.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
screen recording of the bug
selection direction |
||
Created attachment 182236 [details]
selection direction
I can confirm. Additionally, it seems the direction of selection affects which file/files are selected after deleting. When files are selected from top to bottom and deleted, everything is fine. But when files are selected from bottom to top and deleted, then a wrong set of files are selected, instead of the next file.
Merging this in with an existing bug report for the same core issue. Thanks! *** This bug has been marked as a duplicate of bug 504490 *** |
Created attachment 182196 [details] screen recording of the bug SUMMARY Selecting n out of m files in dolphin, where n < m, and then shift-deleting them will lead to random files being selected after the deletion and affected of potential actions (open, delete, ....) without the user knowing STEPS TO REPRODUCE 1. Create a folder with a lot of files, e.g. `for i in `seq 1 20`; do touch $i.txt; done` 2. select some random files in the middle 3. shift delete them OBSERVED RESULT Random other files are now selected (most of the time 1, but I also got multiple) EXPECTED RESULT No files are selected SOFTWARE/OS VERSIONS Operating System: Fedora Linux 42 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.9-300.fc42.x86_64 (64-bit) Graphics Platform: X11