X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=fu8ArQu2jy0pDIuW
	To25O/VoZwf71dfHl5eO8/27JRKI6uV7VtlCcP0wmyfPPMWTL5VxJQLTzeXmluIZ
	Jayckh0MfXi+wxZT8stNVMmsLyB9xCDRF9GwTme3MkpPx69/5dRh4/CKTclmD55V
	0Q6ByI6hdQWnyQL4LTPNID43wWk=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=3gM0tYpWmSfhdwfTNvYmE1
	PzSwY=; b=NqtvgD44ItQAobTeh/wjvv7kZi5GxcvbnrK9ROXI4xUH783qHyiWXT
	zff6LEqJqpcy2dTgcOFaKgi8lwlwEcZYu+9+lV+aHMLceNpTT9TJaQ9CWnhMBBuH
	WUDr/t2GMxCSe8NdsF+fqBIErh0LQq1zpS1tHUccWEBBn+ZyZZLRI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-4.7 required=5.0 tests=AWL,BAYES_40,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=calgary, SYSTEM, mcbroom, McBroom
X-HELO:	smtp-out-no.shaw.ca
X-Authority-Analysis:	v=2.2 cv=f8g4PK6M c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=N659UExz7-8A:10 a=edmN6eEefmPw9Wh6FXQA:9 a=pILNOxqGKmIA:10
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: Window 10 authorization problems
To:	cygwin AT cygwin DOT com
References:	<373b179e-3c50-2478-3559-f096e7710708 AT bellsouth DOT net>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID:	<1df1aa3e-1367-dcac-ed8b-c8e79a92a09e@SystematicSw.ab.ca>
Date:	Sat, 20 Jan 2018 18:39:12 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version:	1.0
In-Reply-To:	<373b179e-3c50-2478-3559-f096e7710708@bellsouth.net>
X-CMAE-Envelope:	MS4wfE01Oq19W8zbaPMscqA0H++FPV+bbVgO/t29NXBscP2iifHljoYKeZv+rpL0wRXp4nBvBpnAg8i6tUwbjd8K5t0qbxnM55nVe+PqRUjdex/MmRQKxeIt XF0v+OwA+vVNe7V1wK8mOdAgWLqVkLypcEsgAwLMHBFXflroPuC4snMYdiG7PeYpK9XDEZQppzrEuQ==
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

On 2018-01-20 16:35, Robert McBroom wrote:
> Troubles through several cygwin releases with getting the files to have the
> right permissions when running startwinx from an initial cygwin64 terminal.
> Messages follow:
> xauth:  /home/mukx/.serverauth.7284 not writable, changes will be ignored
> xauth:  /home/mukx/.Xauthority not writable, changes will be ignored
> xauth:  timeout in locking authority file /home/mukx/.Xauthority
> winInitMultiWindowWM - DISPLAY=:0.0
> winMultiWindowXMsgProc - DISPLAY=:0.0
> winMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5
> winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
> waiting for X server to begin accepting connections .
> winMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5
> winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5
> and so on until the system gives up.
> A directory listing gives:
>   ----------  2 mukx          mukx             0 Jan 18 18:44 .serverauth.7284-c
>   ----------  2 mukx          mukx             0 Jan 18 18:44 .serverauth.7284-l
>   ----------  1 mukx          mukx            54 Jan 18 18:44 .Xauthority
>   ----------  2 mukx          mukx             0 Jan 18 18:44 .Xauthority-c
>   ----------  2 mukx          mukx             0 Jan 18 18:44 .Xauthority-l
> On Window 7 these files are properly read,write for the user.

Normally a problem with no default ACls (DACLs) on the directory; use getfacl
and icacls to view, and setfacl to set up permissions like:

# file: /home/$USER
# owner: SYSTEM
# group: SYSTEM
user::rwx
user:$USER:rwx
group::---
group:Administrators:rwx
mask:rwx
other:---
default:user::rwx
default:user:$USER:rwx
default:group::---
default:group:Administrators:rwx
default:mask:rwx
default:other:---

C:/Users/$USER NT AUTHORITY\SYSTEM:(OI)(CI)(F)
             BUILTIN\Administrators:(OI)(CI)(F)
             $HOST\$USER:(OI)(CI)(F)

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -