From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: New installation of Cygwin64: xinit.sh exit code 3
Date: Sat, 21 Oct 2023 10:21:23 -0600 [thread overview]
Message-ID: <37443047-282b-4db1-9749-3103af074c87@Shaw.ca> (raw)
In-Reply-To: <DB6P18901MB0055F5110CCE7CBF18CC7A24A4DAA@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
On 2023-10-21 04:52, Fergus Daly via Cygwin wrote:
> 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
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-10-21 16:21 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 [this message]
2023-10-22 4:46 ` Fergus Daly
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=37443047-282b-4db1-9749-3103af074c87@Shaw.ca \
--to=brian.inglis@shaw.ca \
--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).