Created attachment 146153 [details] screenshot STEPS TO REPRODUCE 1. Copy some folders (pretty sure the same happens with files) into the Desktop, whose names are long enough to occupy two rows. 2. Move the folders or files around randomly 3. Select one of them and/or move the mouse cursor over one of them I'm not sure exactly what else is required to reproduce. This happens to me all the time but not 100% of the time, so I don't know what additional steps exactly I'm usually but not always doing that I'm not conscious of. OBSERVED RESULT See the screenshot. The blueish rectangle with smoothed edges that highlights the selected or hover-ed folder looks like there are two of them somehow superposed. EXPECTED RESULT That shouldn't happen. Regardless of how many rows of text the filename occupies, the rectangle around the whole thing should be a single solid one. This is particularly annoying because, every single time, I get the false impression that I have accidentally put multiple folders on top of each other (something that shouldn't be possible, I hope it isn't), and that if I delete the folder that I have selected I will be actually deleting another folder together with it without even knowing which one. So I always undo the selection and then click and drag the folder to move it and reveal the one behind, but there's no other folder behind, and by moving the folder, the artifact disappears and it finally looks as it should. I'm sorry, I feel like my English is terrible but I hope I've been able to explain. The screenshot should pretty much speak for itself anyway. Operating System: openSUSE Tumbleweed 20220118 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.3 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics
I have seen this in the past but have not been able to reproduce it in the past month or so with git master packages, which at some point became Plasma 5.24. Can we consider this fixed in Plasma 5.243 for now? You can feel free to re-open it if you till experience the issue after you upgrade to Plasma 5.24.