This is the mail archive of the
mailing list for the Cygwin project.
Re: setup-x86_64: postinstall errors: Package bash 1, Package a2ps 2 and xinit 134
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Tue, 23 Jul 2013 14:14:10 -0400
- Subject: Re: setup-x86_64: postinstall errors: Package bash 1, Package a2ps 2 and xinit 134
- References: <CADex0xx+uY6Y8ngZ3tUsYr+KPi0t0+H+H7X-civ-iq0diuJfZw at mail dot gmail dot com> <51EE0951 dot 90007 at users dot sourceforge dot net>
On 7/23/2013 12:40 AM, Yaakov (Cygwin/X) wrote:
On 2013-07-22 19:52, Kenneth Wolcott wrote:
xinit.sh exit code 134
This is from a SIGABRT in mkshortcut. Chuck?
/usr/bin/mkshortcut $CYGWINFORALL -P .....
where $CYGWINFORALL is probably -A
This is the same bug as this one:
I never replied directly to that message (I was still AWOL at the time),
but I later referenced it here:
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
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?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple