https://bugs.kde.org/show_bug.cgi?id=485353

Zamundaaa <xaver.h...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
                   |ma/kwin/-/commit/7949032411 |ma/kwin/-/commit/10af8375ee
                   |153ebf9d87b0e936b1bc288df12 |8cfb822b5c6bbee3edc9ed93e5f
                   |b38                         |e1a

--- Comment #10 from Zamundaaa <xaver.h...@gmail.com> ---
Git commit 10af8375ee8cfb822b5c6bbee3edc9ed93e5fe1a by Xaver Hugl.
Committed on 23/04/2024 at 12:32.
Pushed by zamundaaa into branch 'Plasma/6.0'.

outputconfigurationstore: don't overwrite output settings with kscreen configs

The existing code overwrites all per-output data with the config from KScreen
every time an output config is found that isn't in the KWin data base yet.
That causes problems like the scale being reset to 1.0 if the user logged
into Xorg before, or resetting it to whatever scale KScreen had saved on
Wayland, which isn't much better.

Instead of doing that, use the KScreen config as inspiration for some specific
output settings, instead of copying it outright. It's not ideal, but it's
better than overwriting settings the user has explicitly set up


(cherry picked from commit 7949032411153ebf9d87b0e936b1bc288df12b38)

M  +24   -15   src/outputconfigurationstore.cpp

https://invent.kde.org/plasma/kwin/-/commit/10af8375ee8cfb822b5c6bbee3edc9ed93e5fe1a

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to