Bugzilla – Bug 130439
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN=yes in /etc/sysconfig does not work
Last modified: 2007-06-22 14:02:32 UTC
When I set DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN=yes in /etc/sysconfig via the YAST2 /etc/sysconfig Editor, the variable is correctly changed in /etc/sysconfig. When restarting X, however, X still starts with the argument -nolisten tcp. Disabling the corresponding line (ServerArgsLocal=-nolisten tcp) in /opt/kde3/share/config/kdm/kdmrc or modifying the test in /etc/X11/xinit/xserverrc does not change the behavior. Only after commenting out ServerArgsLocal=-nolisten tcp in /etc/opt/kde3/share/config/kdm/kdmrc, displays can be sent from a remote machine.
you need to run SuSEconfig after this change.
from reporter: > Entschuldigung. Könnte YAST das nicht automatisch beim Verlassen des > etc/sysconfig-Moduls machen? Ich bin sicher nicht der Einzige, der über sowas > stolpert. Bei Netzwerk- oder Druckerkonfiguration werden die entsprechenden > Änderungen ja auch beim Verlassen des entsprechenden Moduls durch Update der > Konfiguration und Neustart der entsprechenden Dienste übernommen. > Trotzdem vielen Dank für die Antwort. > Wolfgang Braun I agree. I think we have some mechanisms in place for /etc/sysconfig files. yast maintainers, what tag does it need to run SUSEConfig afterwards?
-> yast-maintainers for sysconfig editor comments
Use tag ## Config: xdm (xdm is name of the SuSEconfig module) See /usr/share/doc/packages/yast2-sysconfig/metadata.txt for more information or ask me. The strange thing is that I have the tag there and yast properly starts SuSEconfig xdm. Did you do an update (from which version?) or fresh installation? Please, attach /etc/sysconfig/displaymanager file (it might not be complete, the variable with the comment should be sufficient).
From: Wolfgang Braun <braun@pdi-berlin.de>: This was a fresh installation of SuSE 10.0 (commercial, I only found the number 175-000125-001 on the DVD), with all available online updates as of yesterday. After changing the value in the YAST/sysconfig module we first logged out of the current account, in the second attempt rebooted the machine, but both times ps aux was showing X with the -nolisten argument. I may not have rebooted between the online updates and the occurrence of the error.
Created attachment 55509 [details] /etc/sysconfig/displaymanager
The variable contains the right Config tag, the sysconfig file is correct (aaa_base is not involved in this bug). Please, attach y2log to get more information. (see http://www.opensuse.org/Bug_Reporting_FAQ#YaST)
Created attachment 55675 [details] y2logs according to procedure described on opensuse
I ran into this bug today too. But sadly I didn't look it up here, so I had to find it out all by myself.. In early releases it was enough to just edit the variable in /etc/sysconfig/displaymanger Reading through the X-startup scripts, one does not think that it might be read anywhere else. /etc/X11/xinit/xserverrc seems clear: 31 . /etc/sysconfig/displaymanager 32 test "$DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN" != "yes" && \ 33 args="$args -nolisten tcp" The value is set by SuSEconfig.xdm and SuSEconfig.kdm3. SuSEconfig.xdm sets it in /etc/X11/xdm/Xservers which is used by kdm too. Why is it used in three places?? Is /etc/X11/xinit/xserverrc not enough??
Similar problem when starting X through startx. This is how xserver is started: X :0 -dpi 96 -auth /home/user/.serverauth.3653 -nolisten tcp -nolisten tcp Please notice that "-nolisten tcp" is doubled. Reason: DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN check in /usr/X11R6/bin/startx and in /etc/X11/xinit/xserverrc. One would be enough.
A workaround for this problem is to overwrite /etc/opt/kde3/share/config/kdm/kdmrc with /etc/opt/kde3/share/config/kdm/kdmrc.SuSEconfig. After this operation all works ok, even for the next time we want to change the parameter via yast. The problem seems to be in the original /etc/opt/kde3/share/config/kdm/kdmrc (in fact it has very small dimension respect kdmrc.SuSEconfig) and it wasn't present in the first installations of suse 10.1 (probably some of the last patches brought the error). I tried to debug the error and I discovered that in the function check_md5_and_move() $USERMD5SUM and $OLDMD5SUM were different instead of equal (I compared this with another installation not affected by this bug), so the statement "if test "$USERMD5SUM" != "$OLDMD5SUM" ...etc. etc" matches the first condition instead mathing the "else" condition.
It works for me in 10.3Alpha4+ although I had to use "init 3" and "init 5" command for restarting the X server... The problem with doubled options remains: X :0 -auth /root/.serverauth.3498 -nolisten tcp -nolisten tcp Reassigning to X.org maintainer...
Removing where? When removing from global xserverrc it will no longer be active when using xinit. When removing from startx it will no longer active when the user has its own ~/.xserverrc. Hmm ...
Still no answer to my question. Closing as WONTFIX.