DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=yJBFVg7tYLFqZDgQV33h0Wckyl1z/TCd7+73IUXOXd2
	C6nvjqhMqKMazXStEyMKla7hxgCAjTHt3r2VNUAgaKT4EK+T/NSarE1BQCtZZEtn
	3fW7QLe3d7q20931SYVW5R+pj5k+Dx1SE2CTc29rpzSZTfU78AVxlxtdwuOzM5Jg
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51EEC7F2.5000402@cwilson.fastmail.fm>
Date: Tue, 23 Jul 2013 14:14:10 -0400
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup-x86_64: postinstall errors: Package bash 1, Package a2ps 2 and xinit 134
References: <CADex0xx+uY6Y8ngZ3tUsYr+KPi0t0+H+H7X-civ-iq0diuJfZw@mail.gmail.com> <51EE0951.90007@users.sourceforge.net>
In-Reply-To: <51EE0951.90007@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 7/23/2013 12:40 AM, Yaakov (Cygwin/X) wrote:
> On 2013-07-22 19:52, Kenneth Wolcott wrote:
>> Postinstall errors:
>>
>> Package: xinit
>>      xinit.sh exit code 134
>
> This is from a SIGABRT in mkshortcut.  Chuck?

 From xinit.sh:
	/usr/bin/mkshortcut $CYGWINFORALL -P .....
where $CYGWINFORALL is probably -A

This is the same bug as this one:
http://www.cygwin.com/ml/cygwin/2013-01/msg00261.html

I never replied directly to that message (I was still AWOL at the time), 
but I later referenced it here:
http://cygwin.com/ml/cygwin/2013-06/msg00214.html

> I believe your report has to do with error handling when attempting
> to modify the All User's Desktop, when you don't actually retain the
> elevated permissions necessary to do so.
>
> However, mkshortcut shouldn't *hang* in that case, so it's definitely
> mkshortcut bug. I just haven't had the cycles to track it down and
> fix it. PTC...

...and that's still true.  Is there are way for setup.exe to delegate 
its elevated credentials down to /bin/bash, and thence to 
mkshortcut.exe? Otherwise, even the *fix* for this bug will just make it 
not hang or crash; it will still fail to modify the all-users start 
menu/desktop.

Do we need to extend setup.exe *itself* to accept instructions from 
packages somehow (maybe in the setup.ini?) so that setup.exe *itself* 
can do some of these privilege-requiring tasks?

--
Chuck


--
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