From: Ian Puleston <ipuleston@SonicWall.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: X11 forwarding extremely slow (unusable) after Cygwin upgrade on Dec 23rd
Date: Sat, 28 Dec 2019 11:26:00 -0000 [thread overview]
Message-ID: <BY5PR18MB33611C2867F9EAD91EB51A8EB8250@BY5PR18MB3361.namprd18.prod.outlook.com> (raw)
Hi,
I have a Cygwin installation on a Windows 10 PC, on which I use X-Windows to access a Linux development/build server. All has been working great for a long time, until I rand a Cygwin upgrade on December 23rd, and after that X11 has become pretty much unusable. I normally launch the terminator terminal emulator locally under X, in that I "ssh -Y" to the Linux machine, and then on there I use a number of GUI apps, mainly SlickEdit and BeyondCompare, which run remotely via X11 forwarding to display in windows on my local Windows PC. But since this Cygwin upgrade all of those remote X11 apps are now extremely slow to respond to anything - about 10 to 20 seconds to action any key press or mouse click.
The two machines are on the same Gig-Ethernet LAN segment so there are no latency issues there (ping response time <1mS).
To take any possible problems with those components out of the picture, I tried instead launching xterm under X11 locally, and from it launching Firefox after ssh to the Linux machine, and again I see the same symptoms with that - trying to type into Firefox's address bar takes about 10 seconds per letter.
I had previously updated my Cygwin installation on March 3rd 2019, so this problem has come in sometime between then and now. I've just spent a very long day and a half rolling back the changes as much as I could (by hacking the setup.ini and re-installing previous versions from the local download cache) and eventually managed to get a working hybrid with enough packages rolled back to make the difference, and now X11 is working fine again.
I also tried a new clean install of the latest Cygwin, after deleting my .XWinrc and removing all but the bare minimum from .startxwinrc, and do see the problem with that too.
Is this any known problem? I couldn't find anything obvious in the email archives.
Ian
--
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 reply other threads:[~2019-12-28 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 11:26 Ian Puleston [this message]
2020-01-01 8:41 ` ianpul01
2020-01-02 19:16 ` ianpul01
2020-01-02 20:18 ` Ken Brown
2019-12-28 12:04 ianpul01
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=BY5PR18MB33611C2867F9EAD91EB51A8EB8250@BY5PR18MB3361.namprd18.prod.outlook.com \
--to=ipuleston@sonicwall.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).