Bug 511658 - Random "could not rename file" while cut-pasting files
Summary: Random "could not rename file" while cut-pasting files
Status: RESOLVED DUPLICATE of bug 510810
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-11-05 02:13 UTC by Ángel Navarro
Modified: 2025-11-23 23:21 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
"Could not rename file" [spanish] while moving files (49.99 KB, image/png)
2025-11-05 02:13 UTC, Ángel Navarro 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ángel Navarro 2025-11-05 02:13:42 UTC 
Created attachment 186506 [details]
"Could not rename file" [spanish] while moving files

SUMMARY
The legend "could not rename file" shows up randomly while moving/cutting files and pasting them afterwards. Pasting them again hides the legend and actually performs the move.

STEPS TO REPRODUCE
1. Cut a file.
2. Paste the file somewhere else

OBSERVED RESULT
The legend "could not rename file" shows up

EXPECTED RESULT
The file should move successfully without warning as before

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.5.1
KDE Frameworks Version:  6.19.0
Qt Version: 6.10.0

ADDITIONAL INFORMATION
Comment 1 JanKusanagi 2025-11-10 19:14:05 UTC 
I've been having this for a while too.

I think this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=511408 which is older.
Comment 2 Riccardo Robecchi 2025-11-23 23:21:03 UTC 
This seems to be the same issue reported with bug 510810. If the issue persists after installing KDE Frameworks 6.20, please open a new bug. Thanks!

*** This bug has been marked as a duplicate of bug 510810 ***