Hi Today I learned of KScreen which handles multiple displays and not messing with the calibration curves in the GPU better than the old Display module. This is what KScreen looks like: http://i.imgur.com/lQcrBdz.png This is what the old Display module looks like: http://i.imgur.com/GXPWcwk.png I am writing this report to ask and suggest something: 1- How do I remove the old Display module? I can't find any corresponding ebuild or filename. Someone on IRC suggested "Might be the krandr stuff from kde-base/systemsettings ebuild. Dunno if you can get rid of it without use of INSTALL_MASK (which is dangerous and thus not recommended)". 2- If so, the ebuild should be updated to allow removal of the old stuff in favor of the new KScreen. 3- There is the possibility that the old Display is supposed to remain along with KScreen, though I think this is unlikely. The appropriate devs should comment. The reason I have this doubt is that KScreen does not support all of the things Display used to, e.g. cloning, so either they are designed to work side by side, or the missing feature(s) simply hasn't been implemented yet.
Unfortunately our support of KScreen is quite lacking, but this is a good opportunity to improve it. We can add a new USE flag to systemsettings to disable the old module and pull in kscreen instead. The reason the old module remains upstream is because it's part of kde-workspace which is in bugfix-only mode. It's removed completely in Plasma 5.
I've pushed a commit to the overlay which addresses this. https://github.com/gentoo/kde/commit/f7f5d84c85b6c7f946b94808849648b4cb6ea667
Thank you!
(In reply to Michael Palimaka (kensington) from comment #2) > I've pushed a commit to the overlay which addresses this. > > https://github.com/gentoo/kde/commit/f7f5d84c85b6c7f946b94808849648b4cb6ea667 This commit, and associated USE=kscreen, breaks (kdebase-)startkde, returning me to the CLI when I try to startx. I found the culprit in the ~/.xsession-errors log: startkde:108 unconditionally sources krandrstartup and errors out if it isn't there: . krandrstartup Commenting that line allowed me to startkde and thus startx just fine. =:^) I'd suggest patching the file in kdebase-startkde to make it a conditional source. Matching the conditional sourcing of (user's) startupconfig a few lines up (line 88), the call would look like this: [ -r /usr/bin/startkde ] && . /usr/bin/startkde That avoids having to add IUSE=kscreen to kdebase-startkde, as well.
Thanks for testing! This regression should now be fixed in git. I borrowed a slightly different approach from Fedora to avoid breaking Prefix installations. https://github.com/gentoo/kde/commit/f43a9f34e3d0223a96a60ac9a7506608b665ce26
Thanks, this is in the tree as of 4.11.13.
