Bug 489683 - Paint Duration stuck at 120FPS weird
Summary: Paint Duration stuck at 120FPS weird
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-03 15:36 UTC by Pedro Paulo Monte Pagani
Modified: 2024-07-10 17:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro Paulo Monte Pagani 2024-07-03 15:36:08 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY

For some reason my Paint FPS is at 120FPS, while my Paint amount shows to be 239/240.
I can confirm that my monitor technically shows to be using 240hz meanwhile the feel is indeed 120hz. This issue is not happening on X11 only wayland, when I boot the system it starts normally with the “240hz”, but then it settles down to 119 after, if I open an appliucation my paint duration goes back to 240FPs, then it goes down after some seconds.

STEPS TO REPRODUCE

I have no idea how to actually reproduce this fully

OBSERVED RESULT
Bad FPS feels like 120hz

EXPECTED RESULT
240hz

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 6.1.1
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Wayland (ONLY)


ADDITIONAL INFORMATION
NVIDIA GeForce RTX 3080/PCIe/SSE2

This issue does not  happen on X11 weirdly, only really wayland
Comment 1 Zamundaaa 2024-07-03 18:22:23 UTC
Is this with the 555 driver?
Comment 2 Pedro Paulo Monte Pagani 2024-07-03 18:43:08 UTC
(In reply to Zamundaaa from comment #1)
> Is this with the 555 driver?

Yes, the .02 latest
Comment 3 Zamundaaa 2024-07-10 17:54:16 UTC
Okay, it's a bug in the 555 driver. You can work around it with the kernel boot argument nvidia.NVreg_EnableGpuFirmware=0