Bug 497902

Summary: Flickering windows in the Overview effect
Product: [Plasma] kwin Reporter: rob <m5vqlddc1>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bizyaev, filip.kendes1
Priority: NOR    
Version First Reported In: 6.3.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: log
screencast

Description rob 2024-12-26 11:52:58 UTC
Created attachment 176881 [details]
log

Hi, encountered flickering windows when viewing desktop windows.
Comment 1 rob 2024-12-26 11:55:25 UTC
Created attachment 176882 [details]
screencast
Comment 2 rob 2024-12-26 12:11:54 UTC
Operating System: Arch Linux 
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 36 × Intel® Core™ i9-10980XE CPU @ 3.00GHz
Memory: 125.5 ГиБ of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2
Comment 3 Ilya Bizyaev 2024-12-26 12:16:08 UTC
I confirm a similar problem, also with NVIDIA. In my case, the flickering only manifests after moving the cursor in circles over the presented windows a few times.

Operating System: openSUSE Tumbleweed 20241222
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2

Graphics:
  Device-1: NVIDIA AD104 [GeForce RTX 4070] driver: nvidia v: 560.35.03
  Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: nvidia
    unloaded: modesetting,vesa gpu: nvidia resolution: 2327x1309
  API: EGL v: 1.5 drivers: nvidia
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 vendor: nvidia v: 560.35.03 renderer: NVIDIA GeForce
    RTX 4070/PCIe/SSE2
  API: Vulkan v: 1.3.296 drivers: N/A surfaces: xcb,xlib,wayland
Comment 4 Filip 2024-12-26 18:44:02 UTC

*** This bug has been marked as a duplicate of bug 495791 ***