Date: Wed, 5 Jan 2000 20:30:58 -0500 From: "Isaac Waldron" <waldroni@lr.net> To: "Gustavo Rios" <grios@ddsecurity.com.br>, <questions@FreeBSD.ORG> Subject: Re: X11 Message-ID: <01b901bf57e5$afe968a0$5f72bbd1@camry> References: <Pine.BSF.4.10.10001052246340.61332-100000@vitoria.ddsecurity.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi folks! > i am trying to get X working but all i get is trouble, when i type startx > into the console i have this: > > etosha# startx > > Authentication failed - cannot start X server. > Perhaps you do not have console ownership?^Cxinit: unexpected signal 2 > > /var/log/messages show me this: > Jan 5 22:49:19 etosha Xwrapper: no modules loaded for `xserver' service > > > I am running X 3.3.5! May you help me with this ? > My uname -a output is: > > FreeBSD etosha 3.4-STABLE FreeBSD 3.4-STABLE #0: Wed Jan 5 13:43:01 EDT > 2000 root@etosha:/usr/src/sys/compile/ETOSHA i386 > I had this problem after I upgraded to XFree86 3.3.5 as well. It stems from the use of "plugable authentication modules." Basically, there seems to be a movement to take authentication code (usernames and passwords) out of individual programs and put it into a separate module that is used for every program requiring authentication. What you need to do (or at least what I did), is add lines to /etc/pam.conf that read: xserver auth required pam_permit.so xserver account required pam_permit.so This should allow you to say: % startx and have X work. However, this allows the xserver service to run with no authentication. The pam_permit.so module (I believe, correct me if I am wrong) simply authenticates the program without checking anything out (like a password or whatever). So, since this is just xserver, it should pose major problems, but be warned. Isaac Waldron waldroni@lr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01b901bf57e5$afe968a0$5f72bbd1>