View previous topic :: View next topic |
Author |
Message |
Psiuyo n00b
Joined: 22 Apr 2004 Posts: 50 Location: Calgary
|
Posted: Sat Nov 13, 2004 2:51 am Post subject: Multiple X displays with xdm broken. reason unknown |
|
|
So I've been running multple displays on my laptop for quite a while, recently running multiple displays via both GDM and XDM. GDM and XDM both start up properly on all the vts they are supposed to, the problem comes when trying to log in... they all want to use :0 after a user logs in.
Since the only display that works is :0 (F7), that is ok, but all others (F8+) are broken as they keep trying to connect to display :0 after logging in.
Here is the log from .xsession-errors when trying to log into display 1 on vt08.
Code: |
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Error: Can't open display: :0.0
|
Not much I know, any ideas how to fix this? It doesn't matter what XSESSION is set to in rc.conf, Gnome, Openbox, or even Xsession causes the same problem.
BTW, here is my Xservers for xdm (which hasn't changed since I set this up months ago)
Code: |
:0 local /usr/X11R6/bin/X :0 vt07 -nolisten tcp
:1 local /usr/X11R6/bin/X :1 vt08 -nolisten tcp
|
|
|
Back to top |
|
|
soya Guru
Joined: 29 Jan 2004 Posts: 429
|
Posted: Sat Nov 13, 2004 6:16 pm Post subject: |
|
|
i've benn using gdm in my brother's system since long time ago. Yesterday i updated gdm with the new version in portage, reconfigured entirely and all worked ok. Since a few weeks ago i have a very large list of kde apps and something else related to the system and gnome for update, today i decided to update the system and multiple X using gdm is broken (gdmflexyserver) i can start it but when i try to open a new X it tries to open it in the current X (vts) a message window is sent to the vt7 saying it is current in use and in the vt8 an error is displayed. Some one with the same problem? what can we do?
thanks in advanced _________________ Si el tonto te alaba laméntalo, si el listo te censura piénsalo. |
|
Back to top |
|
|
Caffeine Guru
Joined: 17 Jul 2002 Posts: 401 Location: Melbourne, Australia
|
Posted: Sun Nov 14, 2004 1:20 am Post subject: |
|
|
Psiuyo: I'm having the exact same issue. It's quite annoying. For some reason, the DISPLAY variable is being set to :0.0 instead of 1.0 or 2.0 (Got three running)
If anyone has any ideas, I'd love to hear them. |
|
Back to top |
|
|
Psiuyo n00b
Joined: 22 Apr 2004 Posts: 50 Location: Calgary
|
Posted: Mon Nov 15, 2004 2:47 am Post subject: |
|
|
Well, glad to see it's not just me. I wish I knew what I updated to cause the breakage, but I haven't a clue. I've tried going through and re-emerging the previous versions of recently updated packages that relate to X, but still no go. I may have missed it, or it may be something which I didn't think was X related. I figure sometime in the past two weeks.
Hopefully someone will have a fix soon |
|
Back to top |
|
|
Gentree Watchman
Joined: 01 Jul 2003 Posts: 5350 Location: France, Old Europe
|
Posted: Mon Nov 15, 2004 2:55 am Post subject: |
|
|
Look at etcat -v pam .
I was getting no X at all and some comment about vt7 was about the last output to my X.log before it failed without any error msg.
I found pam-0.77-r1 was bad.
login shows amessage including <XAUTHORITY> , it seems to block X.
HTH. _________________ Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
Back to top |
|
|
Caffeine Guru
Joined: 17 Jul 2002 Posts: 401 Location: Melbourne, Australia
|
Posted: Mon Nov 15, 2004 5:54 am Post subject: |
|
|
Anyone else using gcc 3.4.3? |
|
Back to top |
|
|
soya Guru
Joined: 29 Jan 2004 Posts: 429
|
Posted: Tue Nov 16, 2004 12:11 am Post subject: |
|
|
have you found the solution? do you think pam is broken or breaking something?
Gentree wrote: | Look at etcat -v pam .
I was getting no X at all and some comment about vt7 was about the last output to my X.log before it failed without any error msg.
I found pam-0.77-r1 was bad.
login shows amessage including <XAUTHORITY> , it seems to block X.
HTH. |
_________________ Si el tonto te alaba laméntalo, si el listo te censura piénsalo. |
|
Back to top |
|
|
Psiuyo n00b
Joined: 22 Apr 2004 Posts: 50 Location: Calgary
|
Posted: Tue Nov 16, 2004 12:35 am Post subject: |
|
|
Yeah, I'm using GCC 3.4.3. I thought GCC-3.4.3 would be MORE stable than its predecessors though It's be nice if I could slot 3.4.2 and give it a try, but I'm always leary about backreving a GCC build (had bad breakage in the past)...
Guess I could try reemerging pam with 3.3 for now, but first I have to reemerge GCC 3.3 because that is currently broken as well |
|
Back to top |
|
|
Gentree Watchman
Joined: 01 Jul 2003 Posts: 5350 Location: France, Old Europe
|
Posted: Tue Nov 16, 2004 2:44 am Post subject: |
|
|
FWIW I have been on 3.4.3 for a few months now and have not encountered any issues. _________________ Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
Back to top |
|
|
soya Guru
Joined: 29 Jan 2004 Posts: 429
|
Posted: Tue Nov 16, 2004 2:13 pm Post subject: |
|
|
Gentre can you answer my question? did you find any solution or conclusion?
soya wrote: | have you found the solution? do you think pam is broken or breaking something?
Gentree wrote: | Look at etcat -v pam .
I was getting no X at all and some comment about vt7 was about the last output to my X.log before it failed without any error msg.
I found pam-0.77-r1 was bad.
login shows amessage including <XAUTHORITY> , it seems to block X.
HTH. |
|
_________________ Si el tonto te alaba laméntalo, si el listo te censura piénsalo. |
|
Back to top |
|
|
soya Guru
Joined: 29 Jan 2004 Posts: 429
|
Posted: Tue Nov 16, 2004 7:51 pm Post subject: |
|
|
It seems to be a problem with xhost o DISPLAY, at least in my case althought i'm not sure. I remeber playing with xhost and DISPLAY some days ago when the problem ocurred.
Hope someone can help cause i don't know what to do.
If a open any sesion with startx or gdm all goes well, i can login as a normal user an type "su -" and open any aplication. But if i login with startx -- :1 as a normal user then type "su -" and try to open any app i get an error saying can't connect to :0.0 (of course i'm not on :0.0, echo $DISPLAY tells :0.0, as root, when it should be :1.0 as i can see if i do it with the user i really loged in), after playing with xhost i could do that and open any app , but this time it is opened in my vt7 session, strange, always tries to connect to :0.0. But if i login like i always did with gdm then open a gdmflexyserver and tries to login as the same user i have loged in in vt7, i recieve in vt7 a msg saying kde already opened in vt7. but if i try to login as another user i recieve this
Code: |
/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/:20.Xservers" -h "" -l ":20"
"anna"
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /usr/kde/3.3/bin/startkde
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
xsetroot: unable to open display ':0.0'
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
xset: unable to open display ":0.0"
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
xset: unable to open display ":0.0"
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
xset: unable to open display ":0.0"
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
xsetroot: unable to open display ':0.0'
startkde: Starting up...
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
ksplash: cannot connect to X server :0.0
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
kded: cannot connect to X server :0.0
kded: ERROR: KUniqueApplication: Registering failed!
kded: ERROR: Communication problem with kded, it probably crashed.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
kcminit: cannot connect to X server :0.0
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
knotify: cannot connect to X server :0.0
ERROR: KUniqueApplication: Registering failed!
ERROR: Communication problem with knotify, it probably crashed.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
ksmserver: cannot connect to X server :0.0
startkde: Shutting down...
ICE default IO error handler doing an exit(), pid = 8739, errno = 95
startkde: Running shutdown scripts...
startkde: Done.
|
i think i have to do something with xhost, maybe? hope someone could help, thanks in advanced and sorry for my poor english _________________ Si el tonto te alaba laméntalo, si el listo te censura piénsalo. |
|
Back to top |
|
|
bulash n00b
Joined: 14 Apr 2004 Posts: 63
|
|
Back to top |
|
|
Gentree Watchman
Joined: 01 Jul 2003 Posts: 5350 Location: France, Old Europe
|
Posted: Wed Nov 17, 2004 8:47 am Post subject: |
|
|
There are threads about 3.4.3 being less good than 3.4.2
Down-grading a minor build change should not be catastrophic but look at the relevant threads before jumping in with both feet.
BTW, it's always a good idea to unmask specific version rather than a package in case you did not. I have :
Code: | =sys-devel/gcc-3.4.2-r2
|
@soya:
My conclusion was what I posted: that pam-0.77-r1 is bad. There is a bug report on the issue and I think it may be relevant to this thread.
The solution seemed obvious: mask it.
You can do this using /etc/portage/package.mask , add the following line then emerge pam. It will get set to the previous version.
Code: |
=sys-libs/pam-0.77-r1
|
HTH _________________ Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
Back to top |
|
|
soya Guru
Joined: 29 Jan 2004 Posts: 429
|
Posted: Wed Nov 17, 2004 2:08 pm Post subject: |
|
|
yes, downgrading solved the problem. Also changing editing PAM config file should solve, there are a few lines about DISPLAY and xhost that are denying it all. Thanks to all _________________ Si el tonto te alaba laméntalo, si el listo te censura piénsalo. |
|
Back to top |
|
|
Psiuyo n00b
Joined: 22 Apr 2004 Posts: 50 Location: Calgary
|
Posted: Thu Nov 18, 2004 4:42 am Post subject: |
|
|
Well, downgrading was a big headache... it works now, although it still lists all the gcc-3.4.3 entries in gcc-config, but that's another issue.
I re-emergered pam-0.77-r3 with gcc-3.4.2, but still no fix. I'm trying again with some more conservative flags, and also I'll try re-emerging xorg. Was there anything else you had to re-emerge to make it work? |
|
Back to top |
|
|
bulash n00b
Joined: 14 Apr 2004 Posts: 63
|
Posted: Thu Nov 18, 2004 4:56 am Post subject: |
|
|
Psiuyo: it is hardly a compiler issue. Read this thread and the bug reports. It is all about pam... |
|
Back to top |
|
|
nyda Apprentice
Joined: 12 Aug 2004 Posts: 183
|
Posted: Thu Nov 18, 2004 6:12 am Post subject: |
|
|
Same issue here :/ |
|
Back to top |
|
|
soya Guru
Joined: 29 Jan 2004 Posts: 429
|
Posted: Thu Nov 18, 2004 2:13 pm Post subject: |
|
|
psiyuo, just make sure you're using "pam-0.77" _________________ Si el tonto te alaba laméntalo, si el listo te censura piénsalo. |
|
Back to top |
|
|
adsmith Veteran
Joined: 26 Sep 2004 Posts: 1386 Location: NC, USA
|
Posted: Wed Nov 24, 2004 12:07 am Post subject: |
|
|
Editing the pam_env.conf file worked for me! thanks! |
|
Back to top |
|
|
Caffeine Guru
Joined: 17 Jul 2002 Posts: 401 Location: Melbourne, Australia
|
Posted: Sat Nov 27, 2004 12:57 am Post subject: |
|
|
Editing pam_env.conf work for me also. |
|
Back to top |
|
|
EOvermeer n00b
Joined: 10 May 2004 Posts: 16
|
Posted: Sun Nov 28, 2004 8:12 pm Post subject: |
|
|
Any idea what to edit in the new pam_env.conf ?
I restored the old version and indeed everything works OK now :-)
Thanks |
|
Back to top |
|
|
adsmith Veteran
Joined: 26 Sep 2004 Posts: 1386 Location: NC, USA
|
Posted: Sun Nov 28, 2004 9:36 pm Post subject: |
|
|
Comment out this:
Code: |
#DISPLAY DEFAULT=${REMOTEHOST}:0.0 OVERRIDE=${DISPLAY}
|
And maybe this:
Code: |
#XAUTHORITY DEFAULT= OVERRIDE=@{XAUTHORITY}
|
|
|
Back to top |
|
|
EOvermeer n00b
Joined: 10 May 2004 Posts: 16
|
Posted: Sun Nov 28, 2004 9:46 pm Post subject: |
|
|
adsmith wrote: | Comment out this:
Code: |
#DISPLAY DEFAULT=${REMOTEHOST}:0.0 OVERRIDE=${DISPLAY}
|
And maybe this:
Code: |
#XAUTHORITY DEFAULT= OVERRIDE=@{XAUTHORITY}
|
|
Thank you very much !! |
|
Back to top |
|
|
harrison n00b
Joined: 31 Mar 2003 Posts: 13 Location: Hong Kong
|
Posted: Thu Dec 02, 2004 11:54 am Post subject: Solved with rc3 |
|
|
I just emerged the newest version, rc3 and that worked also! But I checked the pam_env config file to find that in this new version, it is already commented out
Err at least it worked when i tried it with gdmflexiserver |
|
Back to top |
|
|
soya Guru
Joined: 29 Jan 2004 Posts: 429
|
Posted: Thu Dec 02, 2004 10:27 pm Post subject: |
|
|
maybe you didn't run etc-update, in the new version both enviroment variables comes uncommented _________________ Si el tonto te alaba laméntalo, si el listo te censura piénsalo. |
|
Back to top |
|
|
|