| Summary: | Display refresh rates are off by 1000 in wayland | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | grmat |
| Component: | kcm_kscreen | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | meven29, nate, plasma-bugs-null |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 5.14.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
grmat
2017-01-23 13:21:55 UTC
example terminal output:
kscreen.kcm: "ASUS MG279" 1 KScreen::Output(0x1dbcd80)
Connected: true
Enabled: true
Primary: true
Rotation: 1
Mode: "1920x1080@144" @ 143855 Hz
Position: 0 x 0
kscreen.kwayland: Loading Wayland backend.
kscreen.kcm: Saving.
It's a known problem, modesetting is not completed in our Wayland code. Alright, thanks for the answer. I suspect there is no expected timeline? It's one of the topics we'll discuss during the Plasma developer meeting in February. I think it's pretty high on the priority list. Likely 5.10 material given that 5.9 is almost out. I believe this has been fixed, or at least I don't reproduce with Plasma 5.17 Also cannot reproduce. Let's call it fixed. |