Run X via 'startx' after a fresh install, xscreensaver does not run successfully. Xscreensaver states: "Cannot connect to screen :0 session run as root (0/0) running as nobody (99/99) Problems like this are usually due to authorization problems, did you read the manual?" I also notice that if I run X as a normal user, and 'su' in a terminal, I cannot start any X clients as root into that session. The supreme analness of X in RH6.0 is really becomming frustrating, and I know it will be so for many users.
We are working on having a 'su' command that will do xauth stuff. What do you want dave? For us to continue to have a gaping security hole because we were using xhost for a long time when running X with startx? xdm/gdm/kdm have been using xauth for ages. You learn to adapt. can you please tell me why xscreensaver is being run as root? I thought we removed the SUID bit also.
um, I think xscreensaver was running as root for him because he was running as root. :)
fixed in a later xscreensaver release