"G�rard Henry" <[EMAIL PROTECTED]> wrote: > >> just now, my users can't login with gnome but it's always possible with CDE > > > > Were your users able to log in under Gnome earlier? > > yes, i have 30 appliances, and i think 10 users are using gnome > instead of CDE. > > > If so, did anything change recently on the system? (New patches, > > new system configuration, reboot?) > > > nothing
OK, so maybe something *outside* the system changed. A name service, maybe? This: > >> /usr/dt/bin/Xsession[765]: 6053 Hangup > >> X connection to :7.0 broken (explicit kill or server shutdown).^M > >> Xlib: connection to "localhost:7.0" refused by server^M > >> Xlib: Invalid MIT-MAGIC-COOKIE-1 key^M is very very strange. "localhost:7.0" is unlikely to match anything in the user's ~/.Xauthority file. I suspect that what's happening is that something in the Gnome startup is rewriting $DISPLAY in the user's environment from ":7.0" (which is how it starts off) to "localhost:7.0", which is not going to work. Perhaps some script is attempting to rewrite $DISPLAY to be "`hostname`:7.0" but is getting "localhost" back from 'hostname' instead of the machine's actual name. What does 'hostname' show on this system? I'd look through the Gnome startup scripts (including things in the user's home directory like .xinitrc, which Gnome uses -- this is a horrible bug IMO -- and system-wide things like /etc/csh.cshrc since this is a tcsh user, although I'd expect badness in system-wide scripts to mess up CDE sessions too) for anything that modifies $DISPLAY in this way. Rewriting $DISPLAY like this is a bad idea anyway, even if it accidentally ends up with a $DISPLAY that refers to the host's actual name. > > Looks like the X server died. Do any messages appear in > > /var/dt/Xerrors when this happens? > > > yes, something like this: > DPMSSupported: No such device > Can't control power levels > DPMSSupported: Invalid argument > Frame Buffer 0 does not support DPMSDPMSSet: Invalid argument > Power management problems > AUDIT: Thu Dec 2 10:11:00 2004: 18903 Xsun: client 4 rejected from > IP ::ffff:127.0.0.1 port 36224 > Auth name: MIT-MAGIC-COOKIE-1 ID: -1 > > but i don't understand why X server died, because users can always > login with CDE I don't think the X server died, I think it's that the user's $DISPLAY has been mangled in a way that prevents X client programs from finding and presenting the correct X authorization cookie. > Somthing strange again is that i read this messages in /var/dt/Xerrors: > X connection to :3.0 broken (explicit kill or server shutdown).^M > but only for 3 same appliances on 30 appliances! Is it important? > How can we explain this message? If the user session fails then the display manager will kill the X server, which will cause any existing X clients to die with this message. If that's what's happening then these are caused by the failure of the user session, they do not cause the failure. Is it really these appliances that fail, or is it the token (eg if you use smartcards, does the problem follow the smartcard?), or is it the user (can other users get a Gnome session?). > And i want to add that i have a config with 2 servers in failover Are you seeing this problem on both servers. or only on one? > Thanks for your help, i hope i'll find soon a solution, some users > hates CDE... We have people here who still refuse to move off OpenLook. They hate CDE *and* Gnome :-) OttoM. __ [EMAIL PROTECTED] Disclaimer: These are my opinions. I do not speak for my employer. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm _______________________________________________ SunRay-Users mailing list [EMAIL PROTECTED] http://www.filibeto.org/mailman/listinfo/sunray-users
