Bug 503094

Summary: File name glitches when scrolling
Product: [Applications] dolphin Reporter: Ángel Navarro <jesusnavarrojr188>
Component: view-engine: icons modeAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: john.kizer, kfm-devel
Priority: NOR    
Version First Reported In: 25.04.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Video showing the file name glitch.

Description Ángel Navarro 2025-04-21 08:08:23 UTC 
Created attachment 180466 [details]
Video showing the file name glitch.

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
I have the max lines limit set to 2 but there are files that show 3 lines and therefore the name glitches when I scroll. Clicking the window with the mouse "fixes" the glitch until I scroll again.

STEPS TO REPRODUCE
1. Have a file named "Remove-Boot-Warning.tar" (that's the file that's triggering the glitch for me) along with a bunch of another files.
2. Resize the window so you can scroll.
3. Scroll through.

OBSERVED RESULT
The file extension is cloned multiple times all over the place.

EXPECTED RESULT
The filename should:
1- not glitch
2- not show lines over the maximum limit

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Comment 1 Ángel Navarro 2025-04-21 08:12:04 UTC 
EDIT: Forgot to mention: 

To reproduce the bug, you should have "label width" set to small and "maximum lines" set to 2 and use this filename: "Remove-Boot-Warning.tar", which triggered the bug for me
Comment 2 John Kizer 2025-04-22 00:52:23 UTC 
Hi - merging this in with the existing bug report for this issue, thanks!

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