From owner-freebsd-questions Wed May 17 15:15:44 2000 Delivered-To: freebsd-questions@freebsd.org Received: from lab12.ie.pitt.edu (lab12.ie.pitt.edu [136.142.89.102]) by hub.freebsd.org (Postfix) with ESMTP id B386937BF71 for ; Wed, 17 May 2000 15:04:25 -0700 (PDT) (envelope-from grafe@lab12.ie.pitt.edu) Received: (from grafe@localhost) by lab12.ie.pitt.edu (8.10.0/8.10.0) id e4HM4Ch09334; Wed, 17 May 2000 18:04:12 -0400 (EDT) Date: Wed, 17 May 2000 18:04:12 -0400 (EDT) Message-Id: <200005172204.e4HM4Ch09334@lab12.ie.pitt.edu> From: grafe@lab12.ie.pitt.edu (Gary Rafe) To: freebsd-questions@freebsd.org Subject: Re: Problem with X after 3.4 -> 4.0 Cc: cjclark@home.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed this behavior, too, of xinit and Xwrapper last night just after I upgraded from 3.3R/PAO to 4.0R via CDROM on my Toshiba 4030CDT notebook: Authentication failed - cannot start X server Perhaps you do not have console ownership? The server runs just fine when it's made suid. Can someone comment on/document the proper PAM configuration on a 4.0R system for X to run with the correct authorizations ? -- Gary gerst4+@pitt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message