clutz added a comment.
Hi David, there's no bug report for that in the KDE issue tracker (but in our
custom one). I adjusted the patch description above. Is that ok for the kind of
documentation that you want to have? (I would prefer to send you a new
git-patch that contains a complete descr
clutz edited the summary of this revision.
REPOSITORY
R110 KScreen Library
REVISION DETAIL
https://phabricator.kde.org/D6011
To: clutz, davidedmundson
Cc: davidedmundson, plasma-devel, ZrenBot, spstarr, progwolff, lesliezhai,
ali-mohamed, jensreuterberg, abetts, sebas, apol, mart, lukas
clutz edited the summary of this revision.
REPOSITORY
R110 KScreen Library
REVISION DETAIL
https://phabricator.kde.org/D6011
To: clutz, davidedmundson
Cc: davidedmundson, plasma-devel, ZrenBot, spstarr, progwolff, lesliezhai,
ali-mohamed, jensreuterberg, abetts, sebas, apol, mart, lukas
clutz edited the summary of this revision.
REPOSITORY
R110 KScreen Library
REVISION DETAIL
https://phabricator.kde.org/D6011
To: clutz, davidedmundson
Cc: davidedmundson, plasma-devel, ZrenBot, spstarr, progwolff, lesliezhai,
ali-mohamed, jensreuterberg, abetts, sebas, apol, mart, lukas
clutz added a comment.
Thanks David for reviewing that. Oh, I already tried to find the underlying
bug that causes the inconsistency. The debugging led me from libkscreen to
xrandr to libxrandr (XRRGetOutputInfo) to the kernel. Here I noticed the
following things:
1. outputInfo = XRRGet
clutz created this revision.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.
REVISION SUMMARY
There is code for some yet not fixed bug in XRandRConfig::applyKScreenConfig
that should print debug information in case of currentMode is NULL.
