Summary: | XWayland server started by nested KWin Wayland reports incorrect refresh rate | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | sattaxt |
Component: | platform-wayland-nested | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 5.23.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
output from kscreen-doctor-o
output from qdbus output from xrandr |
Description
sattaxt
2021-10-26 10:12:45 UTC
Created attachment 142901 [details]
output from kscreen-doctor-o
Created attachment 142902 [details]
output from qdbus
Created attachment 142903 [details]
output from xrandr
The refresh rate of nested kwin_wayland is hardcoded to 60Hz. Did you mean host kwin_wayland or nested kwin_wayland? host kwin_wayland => kwin_wayland running on top of DRM nested kwin_wayland => windowed kwin_wayland (In reply to Vlad Zahorodnii from comment #4) > The refresh rate of nested kwin_wayland is hardcoded to 60Hz. Did you mean > host kwin_wayland or nested kwin_wayland? I mean kwin_wayland started with "kwin_wayland ... --xwayland ..". This is usually referred to as a "nested session" in KDE documentation I've read, am I using the wrong terminology? (In reply to Vlad Zahorodnii from comment #5) > host kwin_wayland => kwin_wayland running on top of DRM > nested kwin_wayland => windowed kwin_wayland Host. *** This bug has been marked as a duplicate of bug 444303 *** |