This is while using KDE & Dolphin: 1. create file "text" in your home, then "delete" it to trash then again: 2. create file "text" in your home, then "delete" it to trash 3. Open trash and see the files listed as: _File______Folder___ text /home/user text(1) /home/user/text That "/home/user/text" is plain wrong; the file was not deleted from am folder named text! (trash folders are listed without trailing dash "/" ) It works correctly; i can restore that text(1) and it ends up as "test" in /home/user/ Quick test using thunar to delete files to trash: The files in trash is shown by the original name in trash using thunar unfortunately it seem thunar can not show source (original file location) Looking at those files in trash using dolphin they are named like *.2 instead of *(1) (that is irrelevant) but also for them dolphin show wrong path BTW it is even more confusing if user happen to delete a file named "something (1)" twice, dolphin then list a never existed filename "something (2)" in trash, and say it was deleted from folder "whatever/something (1)"
CC: (none) => marja11Assignee: bugsquad => mageia
Still valid Plasma 5.7.1-1 , framework 5.24.0-1
right, i reproduce too. Can you report this bug upstream please ?
I created https://bugs.kde.org/show_bug.cgi?id=366553
Keywords: (none) => UPSTREAM
Assignee: mageia => kde
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=366553CC: (none) => mageia
(In reply to Morgan Leijström from comment #3) > I created https://bugs.kde.org/show_bug.cgi?id=366553 Still opened upstream. Will test this behaviour in next few days with Mageia 8 and Cauldron
Source RPM: dolphin-16.04.1-1.mga6.src.rpm => dolphin-20.12.0-4.mga8.src.rpmVersion: Cauldron => 8Status: NEW => UPSTREAMCC: (none) => ouaurelien
We stopped supporting Mageia 8 almost 8 months ago https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/ That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not. If this particular bug did not get fixed for Mageia 8, then we do regret that. If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field. If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing Mageia is a community project, meaning that we, the users, make Mageia together. The more active contributors we have, the more bug reports will get fixed. Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D
Resolution: (none) => OLDStatus: UPSTREAM => RESOLVED