Bug 492803

Summary: [Regression]. Bug 484179 Strikes Again. Broken Folder Renaming in Dolphin (severely misalligned text).
Product: [Applications] dolphin Reporter: bugreporting
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: filip.kendes1, kfm-devel
Priority: NOR    
Version: 24.08.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot- See how badly the text is misalligned when you rename a file in Dolphin

Description bugreporting 2024-09-08 11:20:22 UTC 
Created attachment 173437 [details]
Screenshot- See how badly the text is misalligned when you rename a file in Dolphin

[Regression]. Bug 484179 Strikes Again. Broken Folder Renaming in Dolphin (misalligned text).

This bug was reported previously [bug.cgi?id=484179/Dolphin 24.02] in KDE 6 and was marked as fixed. Now this annoying bug comes back again with a vengance.

SUMMARY
***
While renaming a folder (F2), Dolphin completely pushes the text and moves it very far to the left, as if you were renaming the empty space between the folders, not the folder itself.
***


STEPS TO REPRODUCE
0. Name your folder "short"
1. Start renaming a folder using backspace.
2. Look where the text is, before you give the folder a new name and before you hit Enter.

OBSERVED RESULT
Text is not under the folder and is moved very far to the left.

EXPECTED RESULT
1. Text under the folder, which is being renamed.
2. Not reintroducing the regression of the regression :(

SOFTWARE/OS VERSIONS
Dolphin 24.08.0
Graphics Platform: X11
Graphics Processor: Intel HD

KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Graphics Platform: X11
Graphics Processor: Mesa Intel® HD Graphics 520
Comment 1 Filip 2024-09-08 11:48:21 UTC 
Original bug report for this is https://bugs.kde.org/show_bug.cgi?id=479695

You can see in that ticket that this should be fixed in Dolphin 24.08.1 and you're using 24.08.0. Wait for the update and if there is still issue in 24.08.1 please report a new bug.

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