https://bugs.kde.org/show_bug.cgi?id=502764
TraceyC <kde...@tlcnet.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |CONFIRMED
Ever confirmed|0 |1
--- Comment #8 from TraceyC <kde...@tlcnet.info> ---
Thank you for taking the time to add all that additional detail. That does help
pinpoint the issue.
I can confirm this on git-master. The bug will only surface if two refresh
rates exist that would round up or down to the next whole number refresh rate
(like 59.939998626708984 and 60)
I do see in the attached kscreen-doctor output that the fractional refresh
rates are being named with the same name as the non-fractional, e.g.
{
"id": "1",
"name": "3840x2160@60",
"refreshRate": 60,
"size": {
"height": 2160,
"width": 3840
}
},
{
"id": "12",
"name": "3840x2160@60",
"refreshRate": 59.939998626708984,
"size": {
"height": 2160,
"width": 3840
}
},
On my system, the kscreen-doctor -j output for one monitor shows the following
refresh rates for its native resolution. You can see that the fractional
refresh rates are rounded up. This doesn't show the bug in the kcm on my
system, because there aren't two fractional refresh rates being set to the same
"name".
❯ kscreen-doctor -j | rg -A 1 -F 'name": "3440x1440'
"name": "3440x1440@85",
"refreshRate": 85,
--
"name": "3440x1440@50",
"refreshRate": 50.000999450683594,
--
"name": "3440x1440@60",
"refreshRate": 59.972999572753906,
--
"name": "3440x1440@144",
"refreshRate": 143.92300415039062,
--
"name": "3440x1440@120",
"refreshRate": 120,
--
"name": "3440x1440@100",
"refreshRate": 99.98200225830078,
--
"name": "3440x1440@75",
"refreshRate": 75.05000305175781,
I'll let the more experienced developers take it from here.
--
You are receiving this mail because:
You are watching all bug changes.
