Click on a file in Dolphin, then click it again to enter the inline filename editing mode. This works most reliably from “Compact” or “Details” file view. “Icons” view sometimes requires an extra click or two to enter filename editing mode.
Even though you are already in filename editing mode, press F2 on your keyboard.
Rename the file and hit Enter.
ACTUAL RESULT: The file fails to rename.
EXPECTED RESULT: The file should now have the new name.
Method #2
Click on a file in Dolphin.
Press F2 on your keyboard twice.
Rename the file and hit Enter.
ACTUAL RESULT: The file fails to rename.
EXPECTED RESULT: The file should now have the new name.
I figured this out while editing a folder containing hundreds of PDF files, and the rename failures usually seemed to happen when I switched back to Dolphin from another application. I always use F2 on my keyboard to rename a file, but when activating Dolphin by clicking on an already-selected file, it would very briefly enter filename editing mode just before my swift F2 keypress was registered, thus triggering the bug.
Perhaps there may be additional ways to trigger the bug as others here have reported, but I’m pretty sure this is what was happening in my case, and why the failures seemed to be so random.
Oh Mr Bumpy, you made me so happy that I can finally reproduce this (without it being in a search result).
That’s absolutely brilliant, so this bug is basically reproducible by pressing F2 whilst already in edit mode…
It’s hardly surprising that nobody could deliberately reproduce it (and folks with the ‘issue’ said it was not 100%).
It really feels like we’ve been trolled for the last month over this… so it’s a USER issue really, but the bug would be that pressing F2 when already in Edit mode should either exit edit mode, or do nothing at all.
So it’d be nice if the other victims of this huge would verify whether it’s the same for them.
From testing a few different Linux live ISO files, I have found that the bug does not occur in Dolphin 25.08.1, but does occur in Dolphin 25.12.3. I’m not sure about versions in-between, but this seems to be a fairly recent regression.
I was just able to test further Dolphin versions thanks to the Windows builds (which exhibit the bug), so now we can pin down the bug’s appearance to somewhere between 25.08.2 and 25.12.1.
The most important version to test is 25.12.0 since it is a major version. That’s where the regression appeared first most likely or at least can reduce further the list of versions to test and then investigate from.
The best way to pick versions to test to detect regression is dichotomy.
For KDE Gears distribution, the first number is a the year, the second, the month, the next a maintenance release number.
Until the fix makes it into my desktop, I took over the F2 keyboard shortcut with a crude hack using xdotool (me being on X11) to simulate the pressing of the Menu key, followed by r.
REPLACES THE MESSAGE ABOVE: I had to remove the code from here because I found issues and I cannot update code here.
@meven tested the fix in the current git and cant reproduce the bug with the git version.
Sure i had the issue before with the current release version on cachyos.
I haven’t been able to replicate this bug, so yes - same as popy
dolphin -v
dolphin 26.04.0
QThreadStorage: entry 4 destroyed before end of thread 0x55e58a085b80
QThreadStorage: entry 3 destroyed before end of thread 0x55e58a085b80
The extra Qt errors are just noise - that appears also with konsole/spectacle, nothing to worry about.
I’m sorely tempted to ask why you think it’s a good idea to press F2 to enter edit mode, and then… press it again.
I accept that it shouldn’t really make a difference, so there is a bug…
Actually there are TWO bugs here The first is that you employed a rather strange tactic to uncover the bug… I believe it’s called ‘out of bounds’ interactions…
Avoiding AI for this one, employing tells me that pressing F2 again should:
Because you don’t have to press F2 two times. Another naturaly way I trigger the bug “all the time”:
Open Dolphin and work in 2 pane mode
Click on a file in one pane
Click on a file in the other pane
Click on the already selectet file in the first pane
Hit F2
Edit the file
Press enter
Filename gets reverted
It also works even more natural:
Open Dolphin
Click on a file
Click on a nother app
Click on the already selected file in Dophin
Instantly Hit F2 (so you don’t see that it goes into edit mode before)
Edit the file
Press Enter
Filename gets reverted
That is like 2 times F2 because clicking on a selected file, even if you come from another pane or app, goes directly into edit mode but clicking on a non selected file just selects it. So my natural habit when i want to rename a file, is click on it and instantly hit F2. This works on non selected files but with this bug not on selected.
So the solution should be that the 2nd F2 does nothing (not turns edit mode of because then you have the problem that it seams that F2 did nothing) OR select a selected file, coming from another pane or app, should NOT go into edit mode, just if you select it a 2nd time from within the same working pane.
I would prefere that both this solutions would be true the same time. Because the first one (2*F2) is just a real bug and the 2nd one "(selecting a file from outside goes strait into rename mode) is just annoying i think .
would verify whether it’s the same for them.
?
tells me that pressing F2 again should: