[newbie] Installation Woes

[Bob and Christine]

Problems:

1. Keyboard.  The right shift key (a) fails to register the first key
stroke upon being depressed  (b) subsequent key strokes are in lower case.
The left shift key is fully operable.
2. Even more serious, during last Sunday's install user and superuser
passwords were made IDENTICAL to eachother!  It should be noted that the
printer could not be made to operate at that time despite Owen's and Tom's
best efforts.  Possibly this may also be involved in the subsequent crash
when making first fumblings toward GNOME from the root login.  I typed
'startx', clicked on the Main Menu Button (footprint), dragged mouse to
Logout selection, then clicked on Yes in a separate window.  That's when
all hell broke loose.
	'X cancel' causes no response in the separate window with a RED
TRIANGLE containing an '!', but a second separate window with a RED CIRCLE
WITH A HORIZONTAL YELLOW BAR permits me to depress a button entitled
'submit a bug report'.  (Above the button is statement 'Application "gmc"
(process 849) has crashed due to a fatal error (segmentation fault).
Please visit GNOME Application Crash page for more info.)  A partial bug
report follows:

	...ssertion 'option menu != null' failed.
AUDIT:  Sat Jan 25 01:58:39 2003: 807 X: client 5 rejected from localhost
Xlib: connection to ": 0.0" refused by Server
Xlib: Cllient is not authorized to connect to  Server
xscreensaver: Can't open display: :0
xscreensaver: initial effective uid/gid was root/root(0/0)
xscreensaver: running as nobody/nobody (99/99)

xscreensaver: Errors at startup are usually authorization Did you read the
manual and the FAG?  Specifically, the parts of the manual that talk about
XAUTH, XDM, and root logins?

	http://www.jwz.org/xscreensaver/man.html

ICE error: Offending minor opcode	=7 (protocol setup)
	Offending sequence number	=5
	Error: class			=SetupFailed
	Severity:			=FatalToProtocol
Reason: A session shutdown is in progress.

waiting for X server to shut down Gdk -Error**: X connection to :0.0 broken
(explicit kill or server shut down).