[1281] in Moira
xregister on SGIs running Irix 6.5; xlogin eit
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Sun Aug 1 16:16:33 1999
Message-Id: <199908012016.QAA04695@mary-kay-commandos.mit.edu>
To: bug-moira@MIT.EDU, rbasch@MIT.EDU
Cc: jhawk@MIT.EDU, zacheiss@MIT.EDU
Date: Sun, 01 Aug 1999 16:16:29 -0400
From: Garry Zacheiss <zacheiss@MIT.EDU>
A user came into the sipb office today needing help registering
for an account. I had them sit down at the Indy in the front of the
office and register for their account. They encountered a problem when
they got to the screen where they select their password where the text
did not fit in the box on the screen, such that they couldn't see the
second password box or the button to go on.
A little experimentation discovered that this size problem
existed oin all the screens, but didn't become a problem until then
because that was the first time a return at the end of the last visible
text box wouldn't take you to the next screen (I think). I was able to
reproduce this on both an O2 and an Indy; I'd speculate it might be some
sort of font lossage. This problem doesn't exist on Suns.
I discovered another problem in investigating this first
one. Attempting to start xregister via xlogin immediately after the
xserver has restarted was able to consistantly get the machine in a
state where it had both an xlogin and an xregister running. Killing the
xserver and letting it restart after this state resulted in a variety of
interesting affects:
* xlogin not responding to any keyboard input.
* the native Irix xdm starting instead of xlogin.
* xregister refusing to start because it couldn't connect to
localhost:1. jhawk hypothesized this had something to do
with xregister being run under xscope.
* multiple xlogins starting. Personal best was 4.
* xlogin window managed by what appears to be twm.
This was reproduced only on an Indy, although I'd guess it
should work on an O2 as well. If you'd like more details, I should be
able to reproduce at least some of these behaviors for you.
Garry
