SUMMARY When you open menu's on websites, Youtube for example and hover the dropdown notification menu it starts a flickering/blinking. Not sure if it's a mouse tracking type of problem or something with plasma as it started happening after upgrading to plasma 6. STEPS TO REPRODUCE 1. Open chromium based browser and navigate to Youtube 2. Open the notification dropdown and hover the mouse around in the menu and let it sit there a minute OBSERVED RESULT Dropdown menu's flicker SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen Threadripper PRO 5945WX 12-Cores Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA T1000 8GB/PCIe/SSE2 Manufacturer: LENOVO Product Name: 30E000MEUS System Version: ThinkStation P620
Could be related to this: https://bugs.kde.org/show_bug.cgi?id=481975
Does it happen in Firefox?
(In reply to Nate Graham from comment #2) > Does it happen in Firefox? No. The scrollbar also flickers in sync with the flickering of the menu's and the menu will flicker when moving the mouse or scrolling after closing it like old frames are displaying. link to video of the flickering. https://streamable.com/znwdze Other symptoms in chromium browsers is hovering the chrome menu in the top right, the three dot menu, it will display the highlighted entry on hover but that lags and jumps all around. When the mouse enters the window everything on the page flickers and even as I type this right now everything flickers in the top menu and when I erase text it will delete and then flicker back into view for a second after it was deleted. It just seems like a general lag in chromium and it bogs everything else down. Only does this in Wayland as well.
Setting this back to reported as the question was answered.
Thanks. It seems like this is a bug in Chromium, either in general, or possible with it being run in XWayland compatibility mode. You might try forcing it to run as a native Wayland app for now, but even if that fixes it, I expect the problem to be in Chromium itself.