From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Nov 9 20:30:10 2004 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95E9116A4CE for ; Tue, 9 Nov 2004 20:30:10 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70C7643D2F for ; Tue, 9 Nov 2004 20:30:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) iA9KUArk010767 for ; Tue, 9 Nov 2004 20:30:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA9KUA2u010760; Tue, 9 Nov 2004 20:30:10 GMT (envelope-from gnats) Resent-Date: Tue, 9 Nov 2004 20:30:10 GMT Resent-Message-Id: <200411092030.iA9KUA2u010760@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, No Name Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EA0716A4CE for ; Tue, 9 Nov 2004 20:24:35 +0000 (GMT) Received: from defiant4.noxa.de (defiant.noxa.de [212.60.197.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61DFB43D1F for ; Tue, 9 Nov 2004 20:24:32 +0000 (GMT) (envelope-from arundel@h3c.de) Received: (qmail 29647 invoked from network); 9 Nov 2004 21:24:27 +0100 Received: from p54856272.dip.t-dialin.net (HELO skatecity) (84.133.98.114) by defiant.noxa.de with AES256-SHA encrypted SMTP; 9 Nov 2004 21:24:27 +0100 Received: from skatecity. (nobody@skatecity [127.0.0.1]) by skatecity (8.13.1/8.13.1) with ESMTP id iA9KOKfI002658 for ; Tue, 9 Nov 2004 21:24:20 +0100 (CET) (envelope-from arundel@skatecity) Received: (from arundel@localhost) by skatecity. (8.13.1/8.13.1/Submit) id iA9KOJYj002657; Tue, 9 Nov 2004 21:24:19 +0100 (CET) (envelope-from arundel) Message-Id: <200411092024.iA9KOJYj002657@skatecity.> Date: Tue, 9 Nov 2004 21:24:19 +0100 (CET) From: No Name To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: ports/73743: XOrg/XFree xauth add/startx problem X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: No Name List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2004 20:30:10 -0000 >Number: 73743 >Category: ports >Synopsis: XOrg/XFree xauth add/startx problem >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Nov 09 20:30:09 GMT 2004 >Closed-Date: >Last-Modified: >Originator: No Name >Release: FreeBSD 5.3-RELEASE i386 >Organization: >Environment: System: FreeBSD skatecity 5.3-RELEASE FreeBSD 5.3-RELEASE #3: Mon Nov 8 01:54:22 CET 2004 arundel@skatecity:/usr/obj/usr/src/sys/ARUNDEL i386 >Description: xorg-6.7.0_1 starts with the following error message: "xauth: (stdin):1: bad add command line" This error gets caused by the startx script. In order to generate a hexkey (MIT-MAGIC-COOKIE-1) for the xauth entry in ~/.Xauthority it uses /dev/urandom. If random (urandom -> random) is not present (kernel or kld), the device node is missing and `xauth add` will fail due to a missing hexkey. This problem is probably also being caused by any previous Xorg and XFree86 port version and very likely appears on all RELENGs that use `devd` instead of the MAKEDEV system (>=RELENG_5). Since `sh MAKEDEV all` on older systems should take care of /dev/random and the link to /dev/urandom it should also be possible to delete the device node from /dev and expereince the very same problems, as in RELENG_5 and higher. This issue however is not connected in any way to the "xauth:(argv):1: bad display name ":0" in "add" command" problem, which is caused by a wrong /etc/hosts syntax (see PR ports/11977) >How-To-Repeat: Be sure to neither have device random compiled into your kernel, nor to have it loaded as a module. then do: `cd && rm .Xauthority && startx` >Fix: 1. Include some info text that will inform the user if the problem occurs and tell him how to fix the problem. 2. Find another way to get a hold of a hexkey, besides /dev/random. Maybe through perl or RTC or whatever. 3. Check if /dev/urandom exists. If it doesn't, use `xauth generate` to create a hexkey for the xauth entry. It doesn't rely on /dev/urandom and thus succeedes in creating the key. >Release-Note: >Audit-Trail: >Unformatted: