https://bugs.kde.org/show_bug.cgi?id=497125
Bug ID: 497125
Summary: Dolphin: Erratic renaming behavior when quickly using
F2 (rename) followed by Delete on a selected file.
Classification: Applications
Product: dolphin
Version: 24.08.3
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: m.benje...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Created attachment 176391
--> https://bugs.kde.org/attachment.cgi?id=176391&action=edit
Visual demonstration of the issue.
### **Summary**
Dolphin: Erratic renaming behavior when quickly using F2 (rename) followed by
Delete on a selected file.
---
### **Description**
#### Steps to Reproduce
1. Open Dolphin and navigate to a folder containing multiple files.
2. Select a file.
3. Quickly press **F2** (to rename the file), then immediately press **Delete**
(to delete the file).
#### Observed Result
- The file is deleted as expected.
- However, the rename text field appears on the next file in the list.
- If the user clicks elsewhere (e.g., in empty space) to cancel the rename
operation, the next file is renamed using the name of the deleted file.
This issue can occasionally occur when using the mouse to rename and delete
files in quick succession, but the behavior is consistently reproducible using
the keyboard.
#### Expected Result
- Once a file is deleted, its name should not impact any other files.
- The rename text field should not appear on any other files after the targeted
file is deleted.
#### Additional Information
- This bug can lead to unintended renaming of files, causing confusion or data
organization issues.
- A video/gif demonstration of the issue is attached to this report for better
understanding.
---
### **Software/OS Versions**
- **Operating System:** KDE Neon 6.2
- **KDE Plasma Version:** 6.2.3
- **KDE Frameworks Version:** 6.8.0
- **Qt Version:** 6.8.0
- **Kernel Version:** 6.8.0-49-generic
---
### **Additional Information**
- **Environment:** Wayland session (but may also occur under X11).
- Attached gif shows the issue occurring with keyboard input.
- The bug is harder to reproduce using the mouse, but similar behavior has been
observed in specific scenarios.
--
You are receiving this mail because:
You are watching all bug changes.
