public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>
Subject: RE: New installation of Cygwin64: xinit.sh exit code 3
Date: Sun, 22 Oct 2023 04:46:03 +0000	[thread overview]
Message-ID: <DB6P18901MB0055E435F5153FEA53D7781AA4D9A@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DB6P18901MB0055F5110CCE7CBF18CC7A24A4DAA@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>

>> Should have added: the file /var/log/setup.log shows no detail beyond
>> 2023/10/21 09:29:46 running: G:\console64\bin\bash.exe --norc --noprofile "/etc/postinstall/xinit.sh"
>> 2023/10/21 09:29:49 abnormal exit: exit code=3
>> 
>> -----Original Message-----
>> 
>> I made a new installation of Cygwin 64 on a new USB stick, including the package xinit.
>> (I use setup -P followed by a longish but far from complete list of required packages ..,..,xinit,..,..)
>> At this first use of setup I got a single error message:
>>        Package: _/xinit xinit.sh exit code 3
>> At 2nd and all subsequent uses of setup (i.e. as update) I get the slightly altered error message:
>>        Package: _/Unknown package xinit.sh exit code 3
>> In practice, any usage of xinit (e.g. to launch xterm) seems to work perfectly well, but the repeated
>> error message at any update transaction (including when empty) is disconcerting.
>> I have not tried an explicit command "bash (or dash) /etc/postinstall/xinit.sh" as - even if this worked -
>> I would prefer to canvass opinion on this minor glitch.
>> All the same - the glitch is recent, despite being minor .. ..

> What filesystem is the drive formatted as: NTFS, ExFAT, FAT32, or other?
> Try rerunning the xinit postinstall script as follows and report the failing 
> command(s) and error messages:
> 	$ CYGWINFORALL=-A /bin/sh -vx /etc/postinstall/xinit.sh

Thank you!
1. The identical error msg occurs on all of NTFS, FAT32, exFAT file systems.
2. The output from your test command is identical on all file systems,
3. The failing commands are the two separate "case .. mkdir .. mkshortcut" sequences that occur
at the end of the xinit.sh script, with consequent error notification as follows:

case $(uname -s) in *-WOW*) wow64=" (32-bit)" ;; esac
+ case $(uname -s) in
++ uname -s
/usr/bin/mkdir -p "$(/usr/bin/cygpath $CYGWINFORALL -P)/Cygwin-X${wow64}"
++ /usr/bin/cygpath -A -P
+ /usr/bin/mkdir -p '/cygdrive/c/ProgramData/Microsoft/Windows/Start Menu/Programs/Cygwin-X'
/usr/bin/mkshortcut $CYGWINFORALL -P -w / -i /usr/bin/xwin-xdg-menu.exe -n "Cygwin-X${wow64}/XWin Server" -a "--quote /usr/bin/bash.exe
 -l -c \"cd; exec /usr/bin/startxwin\"" /usr/bin/run.exe
+ /usr/bin/mkshortcut -A -P -w / -i /usr/bin/xwin-xdg-menu.exe -n 'Cygwin-X/XWin Server' -a '--quote /usr/bin/bash.exe
 -l -c "cd; exec /usr/bin/startxwin"' /usr/bin/run.exe
mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start Menu/Programs/Cygwin-X/XWin Server.lnk" failed; 
does the target directory exist?

case $(uname -s) in *-WOW*) wow64=" (32-bit)" ;; esac
+ case $(uname -s) in
++ uname -s
/usr/bin/mkdir -p "$(/usr/bin/cygpath $CYGWINFORALL -P)/Cygwin-X${wow64}"
++ /usr/bin/cygpath -A -P
+ /usr/bin/mkdir -p '/cygdrive/c/ProgramData/Microsoft/Windows/Start Menu/Programs/Cygwin-X'
/usr/bin/mkshortcut $CYGWINFORALL -P -w / -i /usr/bin/XWin.exe -n "Cygwin-X${wow64}/User script" -a "--quote /usr/bin/bash.exe
 -l -c \"cd; XSESSION_ICON= exec /usr/bin/startx /etc/X11/xinit/Xsession xinit-compat\"" /usr/bin/run.exe
+ /usr/bin/mkshortcut -A -P -w / -i /usr/bin/XWin.exe -n 'Cygwin-X/User script' -a '--quote /usr/bin/bash.exe
 -l -c "cd; XSESSION_ICON= exec /usr/bin/startx /etc/X11/xinit/Xsession xinit-compat"' /usr/bin/run.exe
mkshortcut: Saving "/cygdrive/c/ProgramData/Microsoft/Windows/Start Menu/Programs/Cygwin-X/User script.lnk" failed;
 does the target directory exist?

When I used Explorer to visit C:\ProgramData\Microsoft\Windows\Start Menu\Cygwin-X I was told:
"You don't currently have permission to access this folder"
and clicking on Continue to get access I was told:
"You have been denied permission to access this folder"
There was then offered an option to edit Permissions which I didn't feel like pursuing.

(I am the Administrator on my own standalone Windows machine. The denial of access to Cygwin-X feels odd.
PS I also have Cygwin32 installed and running. I _am_ permitted access to the equivalent folder Cygwin-X (32-bit).)


  parent reply	other threads:[~2023-10-22  4:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21  9:57 Fergus Daly
2023-10-21 10:52 ` Fergus Daly
2023-10-21 16:21   ` Brian Inglis
2023-10-22  4:46   ` Fergus Daly [this message]
2023-10-22 13:47     ` Brian Inglis
2023-10-23 12:05     ` Fergus Daly
2023-10-23 15:41       ` Brian Inglis
2024-05-10  0:55         ` Frank-Ulrich Sommer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DB6P18901MB0055E435F5153FEA53D7781AA4D9A@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM \
    --to=fergusd84@outlook.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).