I hope I'm answering this right. I can start x up fine with the "startx" command as root, but not as any other user (logging in as that user and using "startx", not su). The problem is when xdm loads up, it gives me the login over and over, and the errors in the .xsession-errors files are, I believe, from xdm.
That's interesting about the two different xdm logins, one from 3.3.6 and the other from 4.1.0. I just installed my system with no X and installed 4.1.0, but maybe it did install 3.3.6 by default or something. Maybe I'll try again. Thanks for the help. Ted Spradley wrote: >Ted Spradley wrote: > >>Craig Taylor wrote: >> >>>I looked at the /var/log/XFree86.*.log but they don't have any errors >>>listed, just all the modules that are loaded. >>>My .xsession-errors file has the following: >>>XLib: connection to ":0.0: refused by server >>>XLib: Client is not authorized to connect to server >>>xterm xt error: can't open display: :0 >>> >>At this point an Xserver is running, but it's not authorizing your >>client xterm to connect. This is kinda weird. This is an area where I >>have little knowledge because it "just works" for me. Am I right to >>understand that you logged into a text-mode terminal and ran startx, and >>that's how this .xsession-errors file was created? What do you have in >>your ~/.xinitrc? >> > >Whoa! I just thought of something. Did you start the X server as >root? Maybe something like "sudo startx" or su and then startx? That >would account for the Xserver being able to open the graphics device and >the log file, but the client xterm can't authenticate as the same user >who owns the Xserver. > _______________________________________________ Newbie mailing list [EMAIL PROTECTED] *** To unsubscribe , or change message options, see: http://XFree86.Org/mailman/listinfo/newbie
