325114 2013-09-20 09:05:26 +0000 Fails to delete files with non ascii names 2013-09-20 09:14:57 +0000 1 1 2 Applications dolphin general 16.12.2 Debian stable Linux RESOLVED DUPLICATE 165044 http://bugs.debian.org/723832 NOR normal --- 0 franzschrober dolphin-bugs-null 0 oldest_to_newest 1398368 0 franzschrober 2013-09-20 09:05:26 +0000 This effect was also noticed on wheezy but the following test is on sid. This also seems to happen with konqueror in filemanager mode. I just cannot delete files and recursive deletes just aborts when it finds such a file Reproducible: Always Steps to Reproduce: * Switch to a normal locale setting (just mine for reference) $ locale LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= * Create a file on a Linux FS (ext4 in the test) with non-ascii chars: $ touch l$'\374'.jpg * open dolphin * right click on the created file * select "Move to trash" or press del * right click on the selected file while pressing "shift" and press del * press "Delete" Actual Results: * message box "The file or folder .../l�.jpg does not exist." is displayed * message "Could not delete file ..../l�.jpg." is shown in dolphin * file is still on the filesystem Expected Results: * No message box/errorbar about non existing file is shown * this file is moved to trash (or in the second step really removed) * no other user file than the selected file is deleted/moved 1398370 1 frank78ac 2013-09-20 09:14:57 +0000 Thanks for the bug report. Please note that this isn't a problem that is caused by Dolphin itself, but by the underlying libraries which cannot handle filenames with broken encoding. This has been fixed recently (for KDE SC 4.11, I think), see https://git.reviewboard.kde.org/r/110043/ However, if I understand correctly, the problem will reappear in KDE Frameworks (5) if no other solution is found. *** This bug has been marked as a duplicate of bug 165044 ***