From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: bash 127 errors after upgrade and other install errors
Date: Mon, 13 Jan 2020 02:27:00 -0000 [thread overview]
Message-ID: <20200113112754.3ef22bc5f6574c15d8128f1e@nifty.ne.jp> (raw)
In-Reply-To: <CH2PR10MB421401F71EF79CA2003BFAD68C350@CH2PR10MB4214.namprd10.prod.outlook.com>
On Mon, 13 Jan 2020 00:27:37 +0000
Henry Goss wrote:
> I seem to be getting numerous bash error code 127 errors after updating
>
> It seems to be happening on things like python and MySQL. The processes just return blank
>
> Ex:
>
> Myql
> #returns blank
> >
>
> "echo $?"
> > 127
>
> Additionally, old software I've been using for a while now fail (sort of), involving python and selenium and chrome/gecko driver
>
> Two python processes get started , which both appear to be attempting to read from the same pipe (I think?)
>
> Closing one of the processes will let the program continue, closing the other causes the main execution to stop.
>
> 127 errors go away with a fresh install, the python/selenium halting issue does not.
>
> Are these related, and is there a fix?
Could you please provide the steps to reproduce the problem?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
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
next prev parent reply other threads:[~2020-01-13 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 0:27 Henry Goss
2020-01-13 2:27 ` Takashi Yano [this message]
[not found] ` <CH2PR10MB4214B159F0618FFD1D52D7748C350@CH2PR10MB4214.namprd10.prod.outlook.com>
2020-01-13 5:51 ` Takashi Yano
2020-01-13 5:59 ` Henry Goss
2020-01-16 10:50 ` Andrey Repin
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=20200113112754.3ef22bc5f6574c15d8128f1e@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).