[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-03-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=481716 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-03-05 Thread fililip
https://bugs.kde.org/show_bug.cgi?id=481716 fililip changed: What|Removed |Added Version|5.93.0 |6.0.0 --- Comment #9 from fililip --- Alright, I

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-03-04 Thread fililip
https://bugs.kde.org/show_bug.cgi?id=481716 --- Comment #8 from fililip --- > (which is not the case for Intel) Interesting. I did not have these problems on an Arc A750 at all, even though I was also doing dual-GPU back when I still had it. What's more, these stutters do not happen on

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-03-04 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=481716 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-03-04 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=481716 --- Comment #6 from Zamundaaa --- If it only happens on startup, it shouldn't be relevant. I can think of two reasons this could happen: 1. if atomic commits take a long time, the commit thread can miss frames - this was an issue with amdgpu for a

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-03-04 Thread fililip
https://bugs.kde.org/show_bug.cgi?id=481716 --- Comment #5 from fililip --- Only happens on startplasma-wayland with the env var or connecting a display to the nvidia card, gets displayed only two times, making apps fullscreen doesn't trigger it again. I just thought it's relevant to the

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-03-04 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=481716 --- Comment #4 from Zamundaaa --- > Will the explicit sync protocol address this? No, it's only about app<->KWin synchronization, synchronization with the kernel is ensured by KWin code. > Framebuffer memory not appropriate for scanout Are there any

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-03-03 Thread fililip
https://bugs.kde.org/show_bug.cgi?id=481716 --- Comment #3 from fililip --- I have observed something in dmesg when using the Nvidia card with KWin: [ 303.194078] [drm] [nvidia-drm] [GPU ID 0x0c00] Framebuffer memory not appropriate for scanout [ 303.194258] [drm] [nvidia-drm] [GPU ID

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-02-29 Thread fililip
https://bugs.kde.org/show_bug.cgi?id=481716 --- Comment #2 from fililip --- The stutters still occur on Plasma 6.0.0. Will the explicit sync protocol address this? (I do not have a problem with apps glitching out on xwayland, just desktop wide stutters, even in native Wayland apps.) -- You are

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-02-29 Thread fililip
https://bugs.kde.org/show_bug.cgi?id=481716 --- Comment #1 from fililip --- Note: I set my CPU frequency to 1750MHz minimum, now the framedropping doesn't occur with cursor motion, but there are observable CPU usage spikes on one thread when anything's happening on the screen. -- You are

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-02-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=481716 Nate Graham changed: What|Removed |Added CC||n...@kde.org, |

[kwin] [Bug 481716] KWin drops frames on nvidia (Wayland)

2024-02-23 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481716 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail