dolphin displays and seems to use (internally) a wrong file name (the new name) after trying to rename a file into a too long name (which results in an error) Reproducible: Always Steps to Reproduce: 1. have a file on EXT4. 2. start rename - hit F2 3. paste this too long name (316 chars) into the inline rename box: xxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxx 4. enter Actual Results: error dialog box ("The file myfilenamehere canot be renamed" - in German in my UI) is shown and file appears with the new name. Doing anything in dolphin (e.g. copying) with the file does not work ("file not existent!"). In fact the file was not renamed (confirmed by a shell window and ls). Apparently dolphin thinks it was renamed. After a F5 refresh the old name is shown again, correct. Expected Results: error dialog box and the old name is still shown background info: This is a ext4 file system (255 Bytes allowed for file name only), this is the cause for the correct error dialog box.
Thanks for the bug report. Dolphin does have support for noticing that renaming fails, see bug 319119. I have verified that this still works if renaming fails because of a name conflict. It seems that the job created by KIO::moveAs does not report the error properly in the "renaming fails because the file name is too long case".
Still an issue in KDE Frameworks 5.45.