Created attachment 140305 [details] Window with missing buttons SUMMARY When first opening the Desktop settings app with a slideshow, the control buttons (remove and browse) for each folder are not present. I have to tile the window or change tab to see them appear. Resizing or maximizing would not make them appear. STEPS TO REPRODUCE 1. Open the desktop settings 2. Set to slideshow 4. Notice the buttons for folders are missing 3. Change tab or tile window 4. You should see the 2 control buttons appear OBSERVED RESULT The folder control buttons are not visible initially. EXPECTED RESULT The folder control buttons should always be visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.85 Qt Version: 5.15.3
Created attachment 140306 [details] Window with buttons
Just noticed the buttons appear when the folder list width changes. This is why I thought only tiling and changing tab would make them appear, because I didn't resize the window small enough. So you can also make the buttons appear if you resize the window small enough to change the width of the folder list.
That's odd. Cannot reproduce. Not sure how this bug makes any sense at all. :(
Created attachment 140549 [details] Video describing the issue I can reproduce it on other computers running 5.22.4. Here's is a video which could help understand the issue.
I have investigated this and I have no idea how it could possibly be happening. Is it still reproducibly happening to you?
Created attachment 141410 [details] Buttons too far right Yes I can still reproduce the bug on 2 different computers, both running neon 5.22.5 with KDE Framworks 5.85.0 and Qt 5.15.3. One has a 1920x1080 dual screen setup, the other a single 1366x768 screen. What I noticed is the buttons are in fact here, but too far right. Only the left side of the remove button is clickable as you can see in the screenshot.
Thanks.
*** Bug 448438 has been marked as a duplicate of this bug. ***
I can't personally reproduce this, but I'm not completely surprised because the code for this is pretty bad. I know because I wrote it. I'll see if I can clean it up a bit and hopefully reduce the weirdness.
*** This bug has been marked as a duplicate of bug 426142 ***