Bug 447739

Summary: Header of Kirigami apps (e.g. System Settings, Kinfocenter, System Monitor, Haruna video player) flicker when changed
Product: [Frameworks and Libraries] frameworks-kirigami Reporter: Patrick Silva <bugseforuns>
Component: generalAssignee: Marco Martin <notmart>
Status: CONFIRMED ---    
Severity: normal CC: f.alexander.wilms, matej.starc, nate
Priority: NOR    
Version: 5.89.0   
Target Milestone: Not decided   
Platform: Arch Linux   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=417636
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: video1
video2
vidoe3

Description Patrick Silva 2021-12-31 13:16:44 UTC 
Created attachment 144990 [details]
video1

SUMMARY
This bug was previously mentioned in bug 417636 comment 34, I'm opening this report as requested by Nate.
The headers of Kirigami apps have a flicker, in the attached videos we see the
bug affecting System Settings, but I can also reproduce with other Kirigami apps like Kinfocenter (click on the sections in the left side), System Monitor (click on the pages in the left side) and Haruna video player (open settings and click on its sections in the left side).

OBSERVED RESULT
a flicker affects the header

EXPECTED RESULT
no flicker

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 1 Patrick Silva 2021-12-31 13:17:09 UTC 
Created attachment 144991 [details]
video2
Comment 2 Patrick Silva 2021-12-31 13:17:30 UTC 
Created attachment 144992 [details]
vidoe3
Comment 3 Nate Graham 2022-01-04 21:24:45 UTC 
Confirmed. I suspect this will require a rewrite of the header visibility and switching code as it is very complicated and difficult to understand right now and every attempt to fix bugs introduces new ones.
Comment 4 Matej Starc 2022-12-16 17:46:52 UTC 
I can't reproduce this on current master.  Could you test this again, please.
Comment 5 Patrick Silva 2023-06-15 11:28:29 UTC 
*** Bug 471070 has been marked as a duplicate of this bug. ***