Wolfgang Bauer composed on 2015-04-28 17:50 (UTC+0200):
Felix Miata composed:
Felix Miata composed on 2015-04-28 05:52 (UTC-0400):
In ~/.kde4/share/config/kdedrc is autoload=false under [Module-kscreen], which
works as expected in KDE4, and it's symlinked to ~/.config/kdedrc.
And that is exactly your problem I think. The file should be named kded5rc, so it's no wonder that kded5 doesn't respect it.
I've since tried = same failure to obey Xorg's config via xrandr. I also tried putting it in ~/.kde/share/config/ and in ~/.config/plasma-workspace/ and in ~/.config/plasma-workspace/env/, all to no good.
The entry itself seems to be ok, this is the same as systemsettings5 creates here if I disable the "KScreen 2" service in "Startup and Shutdown".
Please explain where to find this ability. I asked in https://bugs.kde.org/show_bug.cgi?id=317929#c18 and got no response. This is what I see (no sign of KScreen* anywhere): http://fm.no-ip.com/SS/KDE/startStopSettingsK522AS-096.jpg http://fm.no-ip.com/SS/KDE/startStopSettingsK522BS-096.jpg http://fm.no-ip.com/SS/KDE/startStopSettingsK522DS-096.jpg
Is this a new expectation, or breakage, and if breakage, breakage where? Are scripts in /etc/X11/xinit/xinitrc.d/ no longer being run by default?
It's not the desktop session that runs those files, but Xorg itself AFAIK. So if it works in IceWM, I don't really see any "breakage" regarding that.
I just noticed that /usr/lib64 contains both libKF5Screen.so.6 and libKF5Screen.so.5.2.2. Can this be right? I had similar misbehavior upgrading Fedora from KDE4 to K5, which failed to remove 4's kscreen, and I fixed by manually removing 4's kscreen rpm.
If you would have looked, libKF5Screen.so.6 is just a link to libKF5Screen.so.5.2.2. So I see no point in thinking that this is wrong or would cause a problem...
I did look, just not until after clicking send. :-p I also tried renaming those two so they wouldn't be used. Plasma opened far enough that my display reported the desired mode, just not far enough to be of any use. The question also remains why KDM3 is not affected by xrandr, but IIRC both it and KDM4 had the same problem. Maybe there's a better place than /etc/X11/xinit/xinitrc.d/ to put xrandr, but where? Hmmm, I looked and found kscreen5 was not installed, then installed it. That changes the availability within System Settings -> Startup and Shutdown: http://fm.no-ip.com/SS/KDE/startStopSettingsK522BSb-096.jpg Yet, while kded5rc is shown as not running, the xrandr configuration is still ignored. I logged out, deleted *kded5rc, restarted to find it still ignored, opened settings to find it running, stopped it, logged out, looked but did not find ~/.config/kded5rc, and restarted to find it KScreen 2 running again. What's left to try but report a bug? ~/.config/kdedrc works (as symlink from ../.kde/share/config/kdedrc) in Rawhide's K5. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org