gill@m2c.m2c.org (Robert Gill) (02/27/90)
Maybe this has been discussed before, but if so I missed it. CONFIGURATION: VS2000 running Ultrix 3.1/UWS 2.1. Running DECWindows. PROBLEM STATEMENT: When logging in the Xprompter appears to accept the password and looks like it's going to start up the dxsession. But after about 1 1/2 minutes it comes back with the Xprompter again asking for user name & password. WHAT I'VE TRIED: I've switched to MIT Xterms and was consistently able to login with no problems. I switched back to DECwindows and was unable to login, accept as root, and even that was inconsistent. I've tried adding a new user, local to machine (we use yellow pages for password files). This entry had no password and was able to login. I added a password to the new user and was unable to login. I've run fverify on both the X11 subset and the BASE subsets and found nothing out of the ordinary. I've checked the ownership on /dev, /tmp, and /. I've looked in /usr/adm/X0msgs and found nothing unusual. The error log says nothing since the last reboot. Basically I'm stumped. I've called DEC Support and they've suggested a few things (including the fverify), but nothing I've checked or tested has helped. I've even gone so far as to replace the keyboard. I would rather not reinstall or upgrade to UWS 2.2 at this time, but may have to. Any suggestions would be helpful and appreciated. I will summarize if, and when, a solution becomes evident. Thanks in advance for your helpful suggestions/support. Bob Gill, System Operator Mass. Microelectronics Center **************************************************************************** Robert W. Gill (gill@odin.m2c.org) -- Massachusetts Microelectronics Center
coutu@mnemax.zk3.dec.com (Dan Coutu UEG) (03/02/90)
You will see this behavior if a problem crops up during login. The session manager currently only reports a few error conditions and I believe this is what is annoying you. Check to see that file ownership of your login files (.login, .chsrc, .profile, etc.) is correct. Verify that your default.DECterm setup file has you as owner, check that all of these files are readable by you. If there is anything else that you can think of that could cause errors during login (such as file protection, trying to execute a non-existant command, etc.) then clean up those things too. I suspect that the problem is just an error that is happening silently (i.e. YOU can't see the error mesage) and once it is resolved you'll be golden. This is a known problem and being addressed. Dan Coutu coutu@decvax.dec.com Open Systems Group "...he who will not risk, cannot win." - John Paul Jones StdDisclaimer: This is, of course, my own opinion.