https://bugs.kde.org/show_bug.cgi?id=476018
wokim <mequer...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|UPSTREAM |---
Status|RESOLVED |REPORTED
--- Comment #12 from wokim <mequer...@gmail.com> ---
(In reply to fanzhuyifan from comment #11)
> (In reply to Zamundaaa from comment #5)
> > Yes. You can report the modes being generated despite the option being off,
> > and the image being distorted with some of the generated modes at
> > https://gitlab.freedesktop.org/drm/amd/-/issues.
> > VRR not working with any generated modes is already reported at
> > https://gitlab.freedesktop.org/drm/amd/-/issues/2185
>
> Marking as resolved-upstream.
There is a more specific issue there on this:
https://gitlab.freedesktop.org/drm/amd/-/issues/2985.
But the bugs here are also multiple KDE bugs and not just an AMD bug, so it
shouldn't be marked as resolved-upstream.
> (In reply to wokim from comment #7)
> > I also tried Gnome, and they list every refresh rate (all real and all fake
> > refresh rates). And because they use decimals (e.g. 120.00 Hz and 119.94 Hz)
> > I can distinguish between real and fake refresh rates. So it seems very
> > useful to me if KDE (Display Configuration and kscreen-doctor) would also
> > list all refresh rates (and not try hide duplicates) and also show decimals.
>
> I believe this is being tracked in
> https://bugs.kde.org/show_bug.cgi?id=431057
The refresh rates being improperly stored (bug 431057) isn't the only bug here.
The other bugs here are: (1) Display Configuration hides refresh rates which
are visible in kscreen-doctor, and (2) when you apply e.g. the real 120 Hz with
kscreen-doctor it gets set back to the fake 120 Hz after a reboot.
--
You are receiving this mail because:
You are watching all bug changes.
