https://bugs.kde.org/show_bug.cgi?id=417490
Nate Graham changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
CC|
https://bugs.kde.org/show_bug.cgi?id=417490
--- Comment #9 from Frederick Zhang ---
(In reply to Roman Gilg from comment #8)
> Could the KScreen daemon binary be diverted / renamed?
I deleted /usr/share/dbus-1/services/org.kde.kscreen.service in my system and
now KScreen no longer applies its con
https://bugs.kde.org/show_bug.cgi?id=417490
Roman Gilg changed:
What|Removed |Added
Resolution|NOT A BUG |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=417490
--- Comment #7 from Frederick Zhang ---
Can we reopen this ticket?
Even putting the proposed better solution above aside, so far I haven't found a
stable way to detect whether KScreen has done applying its configurations.
Hence although I've already go
https://bugs.kde.org/show_bug.cgi?id=417490
--- Comment #6 from Frederick Zhang ---
> sure, but in this very case, wouldn't it be possible to query the set
> parameters first and then apply the changes over the set parameters?
This is the behaviour that makes most sense to me as well.
And I gues
https://bugs.kde.org/show_bug.cgi?id=417490
--- Comment #5 from m...@bearsh.org ---
(In reply to Roman Gilg from comment #2)
> In general KScreen can't respect manual scripting and will just override
> such efforts when it applies its own settings via X11 protocol.
sure, but in this very case, wo
https://bugs.kde.org/show_bug.cgi?id=417490
--- Comment #4 from Frederick Zhang ---
May I know what the best way is to tell whether KScreen has done applying its
configuration?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417490
Roman Gilg changed:
What|Removed |Added
CC||m...@bearsh.org
--- Comment #3 from Roman Gilg --
https://bugs.kde.org/show_bug.cgi?id=417490
Roman Gilg changed:
What|Removed |Added
Component|xrandr |libkscreen
Assignee|kwin-bugs-n...@kde.o
