[opensuse-kde] [TW] xrandr starting up disregarded or overridden
This is an excerpt from an executable file (currently 177 lines) I use called "setup" in /etc/X11/xinit/xinitrc.d/: #xrandr --dpi 108 --output VGA-0 --mode 1440x900 # ati analog #xrandr --dpi 108 --output VGA1 --mode 1440x900 # intel analog #xrandr --dpi 108 --output VGA-1 --mode 1440x900 # nouveau analog I uncomment whichever of the lines it contains I wish Xorg to use. In ~/.kde4/share/config/kdedrc is autoload=false under [Module-kscreen], which works as expected in KDE4, and it's symlinked to ~/.config/kdedrc. In a fresh installation of TW20150425 with K5, the applicable uncommented line is either being overridden, or disregarded, both by the KDM3 greeter if I boot into graphical, and by startx /usr/bin/startkde when I boot into multi-user or start a Plasma session from KDM3. If I boot into multi-user and just run startx, I get expected results from xrandr in an IceWM session, which is also the results I get from startx /usr/bin/twm and from startx /usr/bin/startkde booted to 13.2 (KDE4), 13.1 (KDE4), Rawhide (K5) and F22 (K5). If instead of using setup I configure Xorg as desired through /etc/X11/xorg.conf.d/, then KDM3 and Plasma both produce expected results. 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? FWIW, I always used to use xorg.conf* to configure X, and prefer that method, but the xrandr option has been forced for some configurations by the absence of bug fixes upstream: https://bugs.freedesktop.org/show_bug.cgi?id=39949 https://bugs.freedesktop.org/show_bug.cgi?id=77321 -- "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
Felix Miata composed on 2015-04-28 05:52 (UTC-0400):
This is an excerpt from an executable file (currently 177 lines) I use called "setup" in /etc/X11/xinit/xinitrc.d/: #xrandr --dpi 108 --output VGA-0 --mode 1440x900 # ati analog #xrandr --dpi 108 --output VGA1 --mode 1440x900 # intel analog #xrandr --dpi 108 --output VGA-1 --mode 1440x900 # nouveau analog
I uncomment whichever of the lines it contains I wish Xorg to use. In ~/.kde4/share/config/kdedrc is autoload=false under [Module-kscreen], which works as expected in KDE4, and it's symlinked to ~/.config/kdedrc. In a fresh installation of TW20150425 with K5, the applicable uncommented line is either being overridden, or disregarded, both by the KDM3 greeter if I boot into graphical, and by startx /usr/bin/startkde when I boot into multi-user or start a Plasma session from KDM3. If I boot into multi-user and just run startx, I get expected results from xrandr in an IceWM session, which is also the results I get from startx /usr/bin/twm and from startx /usr/bin/startkde booted to 13.2 (KDE4), 13.1 (KDE4), Rawhide (K5) and F22 (K5).
If instead of using setup I configure Xorg as desired through /etc/X11/xorg.conf.d/, then KDM3 and Plasma both produce expected results.
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?
FWIW, I always used to use xorg.conf* to configure X, and prefer that method, but the xrandr option has been forced for some configurations by the absence of bug fixes upstream: https://bugs.freedesktop.org/show_bug.cgi?id=39949 https://bugs.freedesktop.org/show_bug.cgi?id=77321
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. -- "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
Am Dienstag, 28. April 2015, 06:02:42 schrieb Felix Miata:
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. 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".
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... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
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
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
Ok, I created a script in /etc/X11/xinit/xinitrc.d/ now with the following content: #!/bin/sh xrandr --dpi 108 --output VGA-0 --mode 1024x768 I tried logging into Plasma5, KDE4, KDE3, and even IceWM, the resolution is changed as expected. (I have to disable KScreen in Plasma5 and KDE4 though of course, otherwise it changes back the resolution according to its settings, Display and Monitor, shortly afterwards) I even tried different displaymanagers, in addition to KDM4, I also tried xdm and sddm (not that I think it matters). And I got the same results with all of them. I also tried in a Tumbleweed VM (KDM4, KDE4), and the xinitrc.d scripts are called there too. So IMHO you must be doing something wrong. I don't see a bug regarding this, everything is working as expected here. I have a suspicion though: the scripts in /etc/X11/xinit/xinitrc.d/ are called by /etc/X11/xinit/xinitrc.common, which in turn is called by /etc/X11/xinit/xinitrc. Do you have those files, in unmodified form? They are part of the package xinit, is this installed? IIANM, you tend to do minimal installs with disabling the automatic installation of recommended packages... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Wolfgang Bauer composed on 2015-04-29 10:56 (UTC+0200):
So IIUYC, your xrandr commands do neither work with KDE3, KDE4, nor Plasma5, right?
They work everywhere tried except in Plasma5 started with startx from multi-user.target in TW.
Hm, how do you determine that kded5rc is "running"? That's a config file...
I miswrote kded5rc where kscreen5 was meant. It's a quote from http://fm.no-ip.com/SS/KDE/startStopSettingsK522BSb-096.jpg I filed a bug: http://bugzilla.opensuse.org/show_bug.cgi?id=929016 -- "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
Am Mittwoch, 29. April 2015, 05:44:25 schrieb Felix Miata:
Wolfgang Bauer composed on 2015-04-29 10:56 (UTC+0200):
So IIUYC, your xrandr commands do neither work with KDE3, KDE4, nor Plasma5, right? They work everywhere tried except in Plasma5 started with startx from multi-user.target in TW.
Well, I tried with startx now, and that works fine here too, on both 13.2 and Tumbleweed.
I filed a bug: http://bugzilla.opensuse.org/show_bug.cgi?id=929016
Ah, right. So you are actually running "startx /usr/bin/startkde"? I can reproduce that here, when I run "startx /usr/bin/startkde", the xinit scripts are not run. But that's not at all specific to Plasma 5. When I run "startx /usr/bin/icewm- session" to start IceWM, the scripts are not run either. So this seems to be just how startx works (might be a bug, but definitely not one in Plasma5). Setting the envvar WINDOWMANAGER instead should work, it calls the init scripts here on 13.2 at least. E.g.: WINDOWMANAGER=startkde startx Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
PS, I forgot to mention: If you want your xrandr commands to have effect for the login screen, you can add them to /etc/X11/xdm/Xsetup... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Wolfgang Bauer composed on 2015-04-29 13:48 (UTC+0200):
If you want your xrandr commands to have effect for the login screen, you can add them to /etc/X11/xdm/Xsetup...
Won't system updates revert whatever changes an admin would make to it? http://fm.no-ip.com/Tmp/Linux/Xorg/setup is my 19kb current version, which I expect to continue to grow. I typically add new lines wherever, rename, then sort renamed back to setup, and copy the new back to the LAN server. That wouldn't do for a modified Xsetup. I tried moving my executable setup file to /etc/X11/xdm/setup but it has no effect on TW greeter screen. -- "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
Am Mittwoch, 29. April 2015, 15:16:20 schrieb Felix Miata:
Wolfgang Bauer composed on 2015-04-29 13:48 (UTC+0200):
If you want your xrandr commands to have effect for the login screen, you can add them to /etc/X11/xdm/Xsetup...
Won't system updates revert whatever changes an admin would make to it?
No. All files in /etc/X11/xdm/ are configuration files and won't be touched by updates.
I tried moving my executable setup file to /etc/X11/xdm/setup but it has no effect on TW greeter screen.
The file name is Xsetup, not setup. You could also put your custom commands to a different file like setup or Xsetup.local or whatever you like to name it, and call that from the standard Xsetup though. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Mittwoch, 29. April 2015, 21:42:58 schrieb Wolfgang Bauer:
I tried moving my executable setup file to /etc/X11/xdm/setup but it has no effect on TW greeter screen.
The file name is Xsetup, not setup.
You could also put your custom commands to a different file like setup or Xsetup.local or whatever you like to name it, and call that from the standard Xsetup though.
PS: As you put your xrandr command(s) into /etc/X11/xinit/xinitrc.d/setup anyway, you could just call that script of course. Add the following line to /etc/X11/xdm/Xsetup, right at the top after the shebang line (and maybe the initial comments): . /etc/X11/xinit/xinitrc.d/setup (notice the '. ' at the beginning) That way you only have to modify one file if you want to change the resolution and have the same resolution on the login screen and in the X session. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Wolfgang Bauer composed on 2015-04-29 22:03 (UTC+0200):
As you put your xrandr command(s) into /etc/X11/xinit/xinitrc.d/setup anyway, you could just call that script of course. Add the following line to /etc/X11/xdm/Xsetup, right at the top after the shebang line (and maybe the initial comments): . /etc/X11/xinit/xinitrc.d/setup (notice the '. ' at the beginning)
That way you only have to modify one file if you want to change the resolution and have the same resolution on the login screen and in the X session.
Done that way would cause setup to be run twice, correct? Is there any reason once shouldn't be sufficient? IOW, if called by Xsetup, it shouldn't be necessary again, while if no DM is running, it would be a required precursor e.g. to startx. My setup is simple now, only at most one line is ever supposed to get executed. To prevent it running after Xsetup used it would require something complicating it, right? All this because upstream doesn't fix its panning and scale bugs (links in OP), enabling those who wish to use xorg.conf* to do the whole config job on every installation as was possible 4 years ago and before. :~( -- "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
Am Mittwoch, 29. April 2015, 16:34:32 schrieb Felix Miata:
Done that way would cause setup to be run twice, correct?
Yes. Once for the login screen, and then again by xinit, when the actual X user session is started.
Is there any reason once shouldn't be sufficient? IOW, if called by Xsetup, it shouldn't be necessary again,
Correct. You can of course also put your commands to /etc/X11/xdm/setup and call that instead (modify the line I gave you accordingly). Then it will only be run once, when the login screen is started, but not at all when using startx. The changed resolution/settings should be taken over to the user X session.
while if no DM is running, it would be a required precursor e.g. to startx.
Correct.
My setup is simple now, only at most one line is ever supposed to get executed.
Well,in your example it doesn't matter if it is called twice anyway.
To prevent it running after Xsetup used it would require something complicating it, right?
It would be possible (and probably not too complicated), but it's probably not worth the effort.
All this because upstream doesn't fix its panning and scale bugs (links in OP), enabling those who wish to use xorg.conf* to do the whole config job on every installation as was possible 4 years ago and before. :~(
Well. I can't help you there. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Wolfgang Bauer composed on 2015-04-29 21:42 (UTC+0200):
Felix Miata composed:
Wolfgang Bauer composed on 2015-04-29 13:48 (UTC+0200):
If you want your xrandr commands to have effect for the login screen, you can add them to /etc/X11/xdm/Xsetup...
Won't system updates revert whatever changes an admin would make to it?
No. All files in /etc/X11/xdm/ are configuration files and won't be touched by updates.
I tried moving my executable setup file to /etc/X11/xdm/setup but it has no effect on TW greeter screen.
The file name is Xsetup, not setup.
My object was to leave Xsetup undisturbed, not add 19k to a file loaded with things I don't understand.
You could also put your custom commands to a different file like setup or Xsetup.local or whatever you like to name it, and call that from the standard Xsetup though.
Someone who understands scripting could do that. I don't see where it should or could go within Xsetup without disrupting the rest of its function. -- "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
participants (2)
-
Felix Miata -
Wolfgang Bauer