https://bugs.kde.org/show_bug.cgi?id=384733
Sebastian Kügler changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #25 from Rainer Finke ---
I upgraded to KDE Frameworks 5.41 in the hope there would be an improvement for
this 4k screen issue on Wayland, but there is not. It would be great if this
could be fixed for Plasma 5.12.
https://bugs.kde.org/show_bug.cgi?id=384733
E.T. Anderson changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #24 from Rainer Finke ---
Sorry for my late reply. The config ~/.local/share/kscreen is not saved after
adjusting the scaling factor for me either. I did modify manually the config
file to show the value "scale": 1.
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #23 from Sebastian Kügler ---
Looking into this, my findings so far:
We don't get a change event in kded after the scale has changed, this means
that the config isn't saved, so it can't be restored.
I'm looking into why we
https://bugs.kde.org/show_bug.cgi?id=384733
David Edmundson changed:
What|Removed |Added
CC||aleix...@kde.org
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #21 from Rainer Finke ---
The config file in ~/.local/share/kscreen seems to be ok (see below). But
Plasma-Wayland seems to ignore it, the scaling factor of 2x is still applied
automatically after login.
[
{
https://bugs.kde.org/show_bug.cgi?id=384733
David Edmundson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #19 from Rainer Finke ---
KDE Frameworks 5.39.0
Plasma 5.11.1
Qt 5.10 beta
After I login to Plasma-Wayland automatically the scaling is adjusted from 1x
to 2x, I can see it as the Plasma logo is increasing the size. I
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #18 from David Edmundson ---
>Is this supposed to work in Plasma 5.11.1 and KDE Frameworks 5.39?
Yes.
What version of frameworks are you running?
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #17 from Rainer Finke ---
Is this supposed to work in Plasma 5.11.1 and KDE Frameworks 5.39? Because I
can't disable the scaling factor of 2x for my 4k screen on Plasma-Wayland, as
soon as I reboot it will always reset
https://bugs.kde.org/show_bug.cgi?id=384733
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=384733
Sebastian Kügler changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #15 from Sebastian Kügler ---
Git commit d16f63b6e64b49f8dbd4742045b0766a8c550b4b by Sebastian Kügler.
Committed on 21/09/2017 at 14:15.
Pushed by sebas into branch 'master'.
inform outputconfiguration clients that a change
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #14 from Sebastian Kügler ---
Git commit 19e96249d78601d77e022a5ae081be8606ed402e by Sebastian Kügler.
Committed on 21/09/2017 at 13:10.
Pushed by sebas into branch 'Plasma/5.11'.
track the config to monitor, save scale
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #13 from Sebastian Kügler ---
Git commit 8719c33eea8f115986990ddfa90de614b8e945ee by Sebastian Kügler.
Committed on 21/09/2017 at 13:10.
Pushed by sebas into branch 'master'.
track the config to monitor, save scale
Summary:
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #12 from David Edmundson ---
We have a few problems:
1) Whoever sends a config to kwin never gets an accepted/failed reply, so they
block updates forever. (see relevant phab)
2) The kwayland code to do that is
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #11 from Sebastian Kügler ---
Git commit 78e8133e934e837ff927673ca6d07218e054c60d by Sebastian Kügler.
Committed on 19/09/2017 at 18:27.
Pushed by sebas into branch 'sebas/scalechange'.
refresh the config after it changed
https://bugs.kde.org/show_bug.cgi?id=384733
Sebastian Kügler changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #9 from David Edmundson ---
The issue only applies to wayland, not also.
Your patch is to a class that is never used on Wayland. I can tell you it won't
work.
mOutput->setScale is called from outputConfig where
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #8 from Sebastian Kügler ---
Yes, but the problem also applies to Wayland, I just haven't been able to test
it, just to hack up a proof of concept patch. Does it work? :)
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #6 from David Edmundson ---
You can't be selecting 1.2...
Either you're not running master or you're not runing wayland.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #7 from David Edmundson ---
Note that there are two code paths for X and wayland, all your comments are
about the X one.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #5 from Sebastian Kügler ---
I'm opening kcmshell5 kscreen, then "Scale display", set the factor to 1.2 and
hit OK on the popup.
>From reading scalingconfig.cpp, you're only writing the scalefactor to
kdeglobals via KConfig
https://bugs.kde.org/show_bug.cgi?id=384733
David Edmundson changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #3 from David Edmundson ---
Scaling does go via Wayland and the compositor.
It's quite plausible I'm not sending this back properly.
How are you setting it to 1.2?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #2 from Sebastian Kügler ---
can you check if the sebas/scalesave branch of kscreen makes a difference?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384733
--- Comment #1 from Sebastian Kügler ---
The problem seems to be that the kcm doesn't save the config (by design), but
the kded5 module does.
On X11, it does so after getting a changed signal from XRandR. There's no such
event for
28 matches
Mail list logo