From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Cygwin/X XWinrc menu no longer launches after recent updates
Date: Tue, 03 Mar 2020 12:35:00 -0000 [thread overview]
Message-ID: <20200303213524.5ddf37854e2eb85eca50ed96@nifty.ne.jp> (raw)
In-Reply-To: <f5b1rq9k4wr.fsf@ecclerig.inf.ed.ac.uk>
On Tue, 03 Mar 2020 12:18:44 +0000
"Henry S. Thompson" wrote:
> Takashi Yano writes:
>
> > Does reverting cygwin1.dll to 3.1.2 help?
>
> In my case, yes it does. The resulting view from pstree is
>
> `-sh,1614 /usr/bin/startxwin
> `-xinit,1645 /home/ht/.startxwinrc -- /usr/bin/XWin :0 -multiwindow ...
> |-XWin,1646 :0 -multiwindow -auth /home/ht/.serverauth.1614
> `-sh,1652 /home/ht/.Xclients
> |-ssh-agent,1664 /bin/env TMPDIR=/tmp /home/ht/.Xclients
> `-xterm,1665 -geometry +0+60 -ls
> `-bash,1666
> `-sh,1684 /home/ht/bin/goE -Y
> `-ssh,1685 ecclerig.inf.ed.ac.uk -Y
>
> Compare this to the 3.1.4 result:
>
> `-sh,2027 /usr/bin/startxwin
> `-xinit,2058 /home/ht/.startxwinrc -- /usr/bin/XWin :0 -multiwindow -auth ...
> |-XWin,2059 :0 -multiwindow -auth /home/ht/.serverauth.2027
> `-sh,2065
Then, this may be caused by the same bug as
https://www.cygwin.com/ml/cygwin/2020-02/msg00197.html
This bug was already fixed in current git head.
--
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-03-03 12:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 5:14 Roland Roberts
2020-03-03 9:53 ` Takashi Yano
2020-03-03 12:18 ` Henry S. Thompson
2020-03-03 12:35 ` Takashi Yano [this message]
2020-03-03 12:40 ` Henry S. Thompson
2020-03-03 12:59 ` Takashi Yano
2020-03-03 21:43 ` Henry S. Thompson
2020-03-03 22:20 ` Brian Inglis
2020-03-03 23:25 ` Brian Inglis
2020-03-04 1:12 ` Henry S. Thompson
2020-03-03 23:46 ` Henry S. Thompson
2020-03-04 19:05 ` Brian Inglis
2020-03-04 19:05 ` Henry S. Thompson
2020-03-04 8:59 ` Roland Roberts
2020-03-08 2:14 ` Roland Roberts
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=20200303213524.5ddf37854e2eb85eca50ed96@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).