Created attachment 167944 [details] Screenshot that shows text of file from windows registry and other example files being so long it creates glitched text SUMMARY When a file has a long name STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Created attachment 167945 [details] Screenshot that shows glitched text remaining on screen
Pressed enter and it turns out that submits it, I didn't finish writing the report ;-; SUMMARY Unsure what exactly triggers this problem, but when a file has long name and/or multiple file extensions/dots in the name (or maybe multiple spaces)? It can cause glitched text that appears outside of the file's allocated space on the screen. This glitched text appears unreliably when switching windows, and when switching folders WITHIN dolphin, the glitched text persists until refreshed. STEPS TO REPRODUCE 1. Have a file with a long name like NTUSER.DAT{c18d6107-b171-11ed-a3b5-c85b76b75115}.TM.blf be displayed within dolphin (This is the actual file name of a file I saw in dolphin while searching through a windows partition) 2. There will be glitchy text that persists even if changing into another folder 3. It goes away with refreshed OBSERVED RESULT Glitchy text appears, below the actual bounds of where the file name should be. This glitchy text is out of bounds and persists on the screen when switching folders, even if the original file is no longer on screen. The text can also become blackened and incorrectly colored. EXPECTED RESULT It is expected that text does NOT appear out of bounds of the file name, and does NOT persist even when folder changes SOFTWARE/OS VERSIONS Operating System: Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.22 (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION
*** This bug has been marked as a duplicate of bug 459395 ***