| Summary: | X only allows on vt7, fails on any other with ":0.0" refused by server | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | SI Reasoning <si> |
| Component: | [OLD] Server | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
initial client xhost xsession
2nd client xsession errors kdm log kdmrc file |
||
|
Description
SI Reasoning
2004-11-19 10:43:34 UTC
Created attachment 44302 [details]
initial client xhost xsession
Created attachment 44303 [details]
2nd client xsession errors
Created attachment 44305 [details]
kdm log
There is an interesting section here where it says:
Unrecognized option: tcp
use: X [:<display>] [option]
maybe this is where the issue is?
regarding the error in kdm log, -nolisten tcp was changed to just tcp but it made no difference (and I think this is for the local xserver anyway) sczjd@gentoo kdm $ cd /usr/kde/3.3/share/config/kdm sczjd@gentoo kdm $ cat Xservers # Xservers - local X-server list # # This file should contain an entry to start the server on the # local display; if you have more than one display (not screen), # you can add entries to the list (one per line). # If you also have some X terminals connected which do not support XDMCP, # you can add them here as well; you will want to leave those terminals # on and connected to the network, else kdm will have a tougher time # managing them. Each X terminal line should look like: # XTerminalName:0 foreign # :0 local@tty1 /usr/X11R6/bin/X tcp #:1 local@tty2 reserve /usr/X11R6/bin/X -nolisten tcp :1 #:2 local@tty3 reserve /usr/X11R6/bin/X -nolisten tcp :2 #:3 local@tty4 reserve /usr/X11R6/bin/X -nolisten tcp :3 #:4 local@tty5 reserve /usr/X11R6/bin/X -nolisten tcp :4 ### Don't change these two lines; they are hints for genkdmconf. ### ### Version 1.99 ### Created attachment 44306 [details]
kdmrc file
there is a new section called VTservers=-7 which I think was there to put it on
the virtual terminal 7 on the local machine but maybe it is a factor?
This is not just a kdm issue. I have the same issue with gdm. The previous comment does not appear to be relevant. switched from XFree86 to xorg but it made no difference. One other piece of info.... I currently do not have the monitor plugged into the host server. Also, whenever X starts via kdm/gdm after a reboot local X is caught in a run condition. With kdm I have to /etc/init.d/xdm stop then kill X, with gdm stopping the xdm service will kill X. When I restart the xdm service for the 2nd time, it will work fine... except for the issue mentioned in this bug report. I have tried to ssh into this computer and run a program and it also fails. So I tried to do an xhost and this also fails: sczjd@gentoo sczjd $ xhost+ -bash: xhost+: command not found sczjd@gentoo sczjd $ xhost + xhost: unable to open display "192.168.1.210:0.0" sczjd@gentoo sczjd $ ifconfig -bash: ifconfig: command not found sczjd@gentoo sczjd $ echo $DISPLAY 192.168.1.210:0.0 sczjd@gentoo sczjd $ xhost +192.168.1.210:0.0 xhost: unable to open display "192.168.1.210:0.0" sczjd@gentoo sczjd $ sudo xhost +192.168.1.210:0.0 xhost: unable to open display "192.168.1.210:0.0" a few more things I have noticed: I can only login remotely via xdmcp using vt7. Any attempt at logging in via xdmcp on any other vt (such as vt8) will fail with the following and then restart the local X: Xlib: Invalid MIT-MAGIC-COOKIE-1 key Auth name: MIT-MAGIC-COOKIE-1 ID: -1 Xlib: Invalid MIT-MAGIC-COOKIE-1 key If I type xhost + on the xdmcp server, It will attempt to login with a different user on vt8 while the first user is logged in on vt7, it will not kick out but it will leave a blank screen. If I then switch over to vt7, it is now acting screwy with open windows slowly migrating upwards and other signs that show that the new login appears to try to be starting up in vt7 instead of vt8. This requires me to shut down X on both vt7 and vt8. If I then log into both vt7 and then vt8 with the same user, an error message stating that "kde appears to already be running" will appear in vt7! In both cases, it appears that the xdmcp server is not recognizing anything outside of vt7. What could cause this? hmmm It seems that I can connect to xdmcp remotely via different clients, but only if I am using :0 (vt7). Something may have partially fixed this, but I was able to connect via cygwin when using :0 still trying to track this down... any clues would be helpful.... I watched top while kde tried to load, it went through a series of kdeinit messages before it kicked out. I then tried XFCE4 and it loaded to a certain point and then kept trying to issue an error message. Unfortunately, I cannot see what this error message is since the thin-client terminal monitor is blue with no visual signs of any window manager activity. (The XDMCP login screen does come up and login seems to work fine). both fluxbox and icewm kick out fast which means they get to the bad section faster. THis is driving me insane.... and I am considering trashing the whole install and starting over, but I would rather just get to the bottom of this. Comment out the ServerVTs section of kdmrc. If that doesnt work, try setting the value to 2 (ie not negative). Furthermore, if you can try the following # Whether KDM should lock the PID file to prevent having multiple KDM # instances running at once. Don't change unless you're brave. # Default is true #LockPidFile=false Set LockPidFile=false and you should be able to spawn more than one kdm session. I tried all three but they had no affect a few additional tests: on the terminal server host, I tried to login via vt8 and it failed just as on the clients THe ServersVt line in kdmrc had no effect, and it should not be a surprise since I have the exact same issue in gdm. However, one interesting thing was, that after I disabled the ServersVT line in kdmrc and rebooted the computer, I ran /etc/init.d/xdm start and it then properly put X in vt7. So at least it appears that the line was not even needed (I may go ahead and add xdm to init 5 again and disable the line to double check). However this does beg the question, if it is an issue with both kdm & gdm, then maybe there is an X setting that is impropper that is causing it. Where there any changes to X that necessitated the need for the VTServers line? Where was that change made and what was the old setting? Maybe if I change it back and it works, then we have something to go on. I am changing the title since this is not limited to xdmcp but also on localhost: I have tried several different ways and config changes such as recommended by the following link: file:///var/tmp/kdecache-sczjd/krun/23727.0.blnewbie4_3_7.htm however they fail with the same error. I currently am using gdm, but have the same issue with kdm. When I log into a session via gdm/kdm on any other vt besides vt7, whether localhost or xdmcp or xnest I get the following error message (if I am not already logged into a session on vt7): #~/.xsession-errors /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:1.Xservers" -h "" -l ":1" "sczjd" /etc/X11/gdm/Xsession: Beginning session setup... Agent pid 14254 KeyChain 2.5.1; http://www.gentoo.org/proj/en/keychain/ Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL * Found existing ssh-agent (13828) * Known ssh key: /home/sczjd/.ssh/id_rsa Xlib: connection to ":0.0" refused by server Xlib: No protocol specified xrdb: Can't open display ':0.0' Xlib: connection to ":0.0" refused by server Xlib: No protocol specified xmodmap: unable to open display ':0.0' /etc/X11/gdm/Xsession: Setup done, will execute: gnome-session Xlib: connection to ":0.0" refused by server Xlib: No protocol specified (gnome-session:14233): Gtk-WARNING **: cannot open display: ------------- Interestingly, after failing when trying to login via vt8, I then logged into vt7 successfully and received the following message via a window entitled "open displays": There are some displays already open. You can select one from the list below or open a new one. Username Display Nobody Display :1 on virtual terminal 8 --------------- below is the ~/.xsession-errors for the successful vt7 login: root@gentoo sczjd # cat .xsession-errors /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "sczjd" /etc/X11/gdm/Xsession: Beginning session setup... Agent pid 14483 KeyChain 2.5.1; http://www.gentoo.org/proj/en/keychain/ Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL * Found existing ssh-agent (13828) * Known ssh key: /home/sczjd/.ssh/id_rsa /etc/X11/gdm/Xsession: Setup done, will execute: gnome-session SESSION_MANAGER=local/gentoo:/tmp/.ICE-unix/14462 esd: Esound sound daemon already running or stale UNIX socket /tmp/.esd/socket This socket already exists indicating esd is already running. Exiting... audio_alsa: no cards found! audio_alsa: no cards found! audio_alsa: no cards found! ** (gnome-session:14462): WARNING **: Esound failed to start. (gnome-session:14462): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gnome-session:14462): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", Window manager warning: Log level 16: Unable to locate theme engine in module_path: "redmond95", Window manager warning: Log level 16: Unable to locate theme engine in module_path: "redmond95", (gdmflexiserver:15343): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gdmflexiserver:15343): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gnome-panel:15339): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gnome-panel:15339): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (nautilus:15337): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (nautilus:15337): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gnome-terminal:15341): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gnome-terminal:15341): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", audio_alsa: no cards found! audio_alsa: no cards found! ----------------------------- nothing obvious above but shown for comparisons sake. Now the fun part, with a current session running on vt7, I login via vt8. Instead of instantly kicking me out, it instead tries to run on vt7. ~/.xsession-errors root@gentoo sczjd # cat .xsession-errors /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:1.Xservers" -h "" -l ":1" "sczjd" /etc/X11/gdm/Xsession: Beginning session setup... Agent pid 16074 KeyChain 2.5.1; http://www.gentoo.org/proj/en/keychain/ Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL * Found existing ssh-agent (13828) * Known ssh key: /home/sczjd/.ssh/id_rsa /etc/X11/gdm/Xsession: Setup done, will execute: gnome-session SESSION_MANAGER=local/gentoo:/tmp/.ICE-unix/16053 esd: Esound sound daemon already running or stale UNIX socket /tmp/.esd/socket This socket already exists indicating esd is already running. Exiting... audio_alsa: no cards found! audio_alsa: no cards found! audio_alsa: no cards found! ** (gnome-session:16053): WARNING **: Esound failed to start. (gnome-session:16053): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gnome-session:16053): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", gnome-smproxy: already running on display :0.0 Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. (gnome-panel:16429): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gnome-panel:16429): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gnome-panel:16429): Gtk-WARNING **: Ignoring the separator setting Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. (nautilus:16431): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (nautilus:16431): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gdmflexiserver:16441): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (gdmflexiserver:16441): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. audio_alsa: no cards found! From another buglist discussion that dovetailed to this issue: ------- Additional Comment #23 From STefan 2005-02-03 03:10 PST ------- The prob in your other bugreport could come from xorg, I have also a problem with exporting applications since I installed xorg, xorg has a little bug which causes those $DISPLAY messages ------- Additional Comment #24 From SI Reasoning 2005-02-03 11:38 PST ------- I am not convinced that those error messages are the issue though. I was having the same issue reported in bug 71776 with XFree86 and it continued when I transferred to xorg. Now the error message may be an xorg issue, but I am not convinced that it is THE issue. What might help is to have a list of configuration files that might affect the issue and a sample of each running on a system that does not have this problem. I could then run a diff and try to change a few configuration options to see if that is the issue. resolved!!!! The issue is with app-misc/screen-4.0.2-r1 I found the following message and followed instructions and multi-user mode is working again: * Some dangerous key bindings have been removed or changed to more safe values. * For more info, please check /etc/screenrc * * screen is not installed as setuid root, which effectively disables multi-user * mode. To enable it, run: * * chmod u+s /usr/bin/screen * chmod go-w /var/run/screen This was a pretty major change for such a little note that can often be missed on larger updates. It would be nice to have these notes a bit more easily accessed such as a file /var/log/emerge-warnings or something like that and have a message similar to the one for etc-update at the end of an emerge to check this file for special conditions.... OK, thanks. Configuration problem. |
