From owner-freebsd-current@freebsd.org Tue Aug 13 02:56:32 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4F4DBC961E for ; Tue, 13 Aug 2019 02:56:32 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [174.136.98.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 466y6731WJz4KWH for ; Tue, 13 Aug 2019 02:56:31 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.206] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 1c56ff02 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 13 Aug 2019 02:49:49 +0000 (UTC) Subject: Re: 13.0 Current - r350702 exposed a Xorg failure To: "Clay Daniels Jr." , "freebsd-current@freebsd.org" References: From: Pete Wright Message-ID: <8b73d162-e293-2ead-b6b0-b79325b24346@nomadlogic.org> Date: Mon, 12 Aug 2019 19:49:49 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 466y6731WJz4KWH X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 174.136.98.114 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-5.78 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nomadlogic.org]; RECEIVED_SPAMHAUS_PBL(0.00)[239.162.243.23.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.50)[ip: (-9.31), ipnet: 174.136.96.0/20(-2.89), asn: 25795(-0.24), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2019 02:56:32 -0000 On 8/9/19 8:56 PM, Clay Daniels Jr. wrote: > I was eager to load the new 13.0 Current snapshot yesterday as I wanted to > play with the new FUSE tools. I was running 13.0 Current r350491 from last > week and everything was going great. So last night, a little late I guess, > I wiped the older install and loaded r250702. Then I loaded Xorg, all 172 > packages, and loaded the drm-kmod video driver kernel modules, and then ran > startx (as user of course). I got errors & it was late so today I looked > closer. It said: > "xauth: file .serverauth.1039 does not exist" > > Well, this file is apparently something created automatically. I played > with the half-running install for a long time. It ran fine in console mode. > Then I the wiped it and reloaded the same newer r350702. No Go. > > Wiped the new r350702 and reloaded the older r350491 that was working just > fine last night. Same Problem....serverauth.xxx > > Now, I do know that the drm-kmod was the same (g20190710) that had worked > for me at least two times already. I do not know if the Xorg pkg is the > same. I couldn't find a date other than "latest". I'm writing this email > from my Linux partition. first thing that comes to mind, did you make sure to add your user to the "video" group?  this doesn't sound related though...this does sound like a local configuration issue.  iirc when i ran into this problem in the past it was due to permissions, either a .serverauth file owned by root or a UID that no longer exists. -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA