https://bugs.kde.org/show_bug.cgi?id=449212
--- Comment #12 from Fabian Vogt <[email protected]> --- I was able to reproduce bug 449321, which might be related. The KCM saves changes to ~/.local/share/kscreen/control/configs/<hash of outputs>, which are at some point read by the KDED module, applied and the resulting config saved to ~/.local/share/kscreen/<hash of outputs>. On startup, kwin_wayland reads the latter, if it exists. This is an issue if first a configuration in the wayland session is created with e.g. 125% scale, but later on an X11 session started again. Once the KDED module notices a change (manual or automatic, but not sure about the latter), it immediately overwrites the ~/.local/share/kscreen/<hash of outputs> file created in the wayland session, but with "scale": 1 because the xrandr backend does not support per-output scaling. The result is that on the next start of kwin_wayland, a 100% scale is applied initially. If rm -r ~/.local/share/kscreen and recreating the config in the wayland session helps, then this is probably the same as bug 449321. If not, this bug is most likely a different issue. Unfortunately there's no logging of what kwin_wayland does on startup. > Can reproduce. For me, this started happening with 100% reproducibility after > d53fd656e8e91835fbb4b5e37e32bb32dfd6e445 in plasma workspace. That should not influence Wayland applications, but I guess it changed the startup sequence just enough for a race condition to have a different outcome. -- You are receiving this mail because: You are watching all bug changes.
