| Summary: | When monitor supports 59.94hz refresh rate, it does not appear in the refresh rate combobox, but choosing 60Hz sets the refresh rate to 59.94hz | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | mercuriete <mercuriete> |
| Component: | kcm_kscreen | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | minor | CC: | meven29, nate, plasma-bugs-null, thefahre, valdikss |
| Priority: | NOR | ||
| Version First Reported In: | 5.18.5 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=431057 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
mercuriete
2020-08-04 09:14:36 UTC
Posible implementation: when iterating for all refresh rates... if they are rounded to the same number on the dropdown... if the refresh rate is a default videomode dont deduplicate or discard the others refresh rates with the same number. Another implementation: use 2 decimal points on the drop down. I think this is related to https://bugs.kde.org/show_bug.cgi?id=423576 but is not the same bug. What does `kscreen-doctor -o` returns ? And the content of .local/share/kscreen when the bug occurs ? Just a side note unrelated to a bug: 59.94 _is_ a proper mode computed with CVT Reduced Blanking algorithm. It reduces pixel clock requirement and resulting in slightly better power saving. You should prefer 59.94 to 60 wherever possible. Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26? If it is, please change the status to CONFIRMED when replying. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot! (In reply to Nate Graham from comment #6) > Thank you for the bug report. Unfortunately we were not able to get to it > yet. Can we ask you to please check if this is still an issue with Plasma > 5.25 or 5.26? > > If it is, please change the status to CONFIRMED when replying. If not, or if > you can't because you no longer use this setup, you can change the status to > RESOLVED WORKSFORME. Thanks a lot! This is still an issue as of KDE 5.25.4 on Fedora 35. Thanks. Can you paste the output of `kscreen-doctor -o` after you've reproduced the issue? (In reply to Nate Graham from comment #8) > Thanks. Can you paste the output of `kscreen-doctor -o` after you've > reproduced the issue? Unfortunately, no, I won't be able to use the PC this or next week. See my bug 431057, it contains more information. It's not exactly the same bug, but the root could be the same. Similar, yeah, and possibly the same issue. Ironically Bug 431057 shows that we store the refresh rate as a floating point value, probably to support the case of a refresh rate of 59.94hz. But apparently it's not working, since you have this bug too, and storing the data that way also causes Bug 431057. What a mess! Does this happen in Plasma 6? There were some changes regarding fixing kscreen mode and output device mode mapping 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |