Am Dienstag, 28. April 2015, 15:34:10 schrieb Felix Miata:
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.
In openSUSE, ~/.kde/share/config is KDE3's config directory, so of course that doesn't have any effect. And you should not put it to ~/.config/plasma-workspace/ ~/.config/plasma- workspace/env/ either, those are for scripts to be called on login, not for kded5's settings. Again, the file should be ~/.config/kded5rc, and it should contain this: [Module-kscreen] autoload=false I cannot guarantee you that the exact same file works for KDE4 and Plasma5 though, as it contains more than just whether KScreen is to be started or not. So maybe try with a real file instead of a symlink as a test.
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
At the same place where you would find it in KDE4. It should be in the list in "Background Services" (your 2nd picture). It is here. If not, check that you have "kscreen5" installed.
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.
Well, if something is linked against a library and that library is missing, that something won't start.
The question also remains why KDM3 is not affected by xrandr, but IIRC both it and KDM4 had the same problem.
So IIUYC, your xrandr commands do neither work with KDE3, KDE4, nor Plasma5, right? Well, maybe they are run too soon then or something like that? For the record, I just tried putting a script that runs "kdialog --msgbox Test" (to be easily able to see whether it's run or not) to /etc/X11/xinit/xinitrc.d/, and that kdialog message box does indeed popup when I log into Plasma 5. So this seems to be working fine, with KDM4 on 13.2 at least (I will try in my Tumbleweed VM in a minute). I hope your script is actually executable?
Maybe there's a better place than /etc/X11/xinit/xinitrc.d/ to put xrandr, but where?
You could put a script that runs your xrandr commands to ~/.config/plasma- session/env/ for Plasma5, ~/.kde4/env for KDE4, or ~/.kde/env for KDE3 (although KDE3 does not have KScreen and should respect your Xorg, KScreen was new in KDE 4.11). Or configure your script to be run on startup in KDE's settings (Startup and Shutdown->Autostart, I don't know at the moment where this is on KDE3 though). Or you could also run them in ~/.xinitrc I suppose. These options are user-specific though of course, not system-wide.
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
All right. If you disable KScreen there, it should not change the screen's resolution.
Yet, while kded5rc is shown as not running, the xrandr configuration is still ignored.
Hm, how do you determine that kded5rc is "running"? That's a config file...
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.
Of course KScreen 2 is enabled again if you remove kded5rc. That's the default. And it's also obvious that kded5rc is ignored and missing if you delete it. What do you want to tell with this?
What's left to try but report a bug? ~/.config/kdedrc works (as symlink from ../.kde/share/config/kdedrc) in Rawhide's K5.
Again, in openSUSE it should be ~/.kde4/share/config/kdedrc and ~/.config/kded5rc. I haven't tried it myself (but will do so shortly), but I see no reason why that shouldn't have any effect. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org