Re: Cygwin unable to resolve hostnames

> > I'm not sure when this started, but recently Cygwin has been unable to > > resolve (certain) hostnames. > > > > Example: > > wget github.com > > --2015-07-22 15:17:04-- http://github.com/ > > Resolving github.com (github.com)... failed: Non-recoverable failure > > in name resolution. [snip]

Re: Cygwin unable to resolve hostnames

The only thing in that list of interfaces that have IP is the "Ethernet adapter Ethernet0". Right of my head I don't see anything obviously wrong. My first suggestion would be to disable IPv6 on the adapter, just on the odd chance that it is the cause. After that I would start ping'ing the

X won't start

Hello, I just got a new Windows 10 PC at work and I can't seem to get X to start. Here is the log file: $ cat /var/log/xwin/XWin.0.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.17.4.0 OS: CYGWIN_NT-10.0-WOW STI237 2.3.1(0.291/5/3) 2015-11-14 12:42 i686 OS: Windows 10

Crash X11 with 3 commands

I was experimenting with Xterm escape sequences - trying to resize/reposition a window while its iconized and found I can crash X11 in just 3 escape commands in an Xterm (which I have in a shell script): --- #!/bin/bash -x # Iconify

Trivial fix to last change

cygwin1.dll doesn't build on x86 after the last commit (eed35ef). The trivial patch attached fixes it. Ken From 1cd61c54994b2ba6c6ec1d1f8f1249f5f8fd4af3 Mon Sep 17 00:00:00 2001 From: Ken Brown Date: Fri, 11 Dec 2015 17:08:28 -0500 Subject: [PATCH] Fix regparm attribute of

__STRICT_ANSI__ and stdio.h

Hi, is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to glibc's? especially, i meant routines in POSIX 1003.1:2001 (popen(), pclose(), etc). for a specific example, see a cparser issue[1] i submitted. Peace, - [1] https://github.com/MatzeB/cparser/issues/10 -- Problem

Re: Crash X11 with 3 commands

On Fri, Dec 11, 2015 at 9:21 AM, Nem W Schlecht wrote: > Can anybody else confirm? (WARNING - if it does, it'll kill all your > X11 windows! Be careful.) Same here, kills the xterm as well as XWin.exe -- Jim Reisert AD1C, , http://www.ad1c.us -- Problem reports:

Re: Crash X11 with 3 commands

On 11/12/2015 18:54, Jim Reisert AD1C wrote: On Fri, Dec 11, 2015 at 9:21 AM, Nem W Schlecht wrote: Can anybody else confirm? (WARNING - if it does, it'll kill all your X11 windows! Be careful.) Same here, kills the xterm as well as XWin.exe not on my W7-64 cygwin2.4.0-0.9

Updated: tesseract-ocr-3.04.00-3

Version 3.04.00-3 of packages libtesseract-ocr_3 tesseract-ocr tesseract-ocr-devel tesseract-training-util are available in the Cygwin distribution: Other language specific data are available upstream https://github.com/tesseract-ocr/tessdata while training data for building

Updated: leptonica-1.72-2

Version 1.72-2 of packages leptonica libleptonica-devel libleptonica_3 are available in the Cygwin distribution: CYGWIN CHANGES Modified tmp default dir settings that impacted tesseract training script. CHANGES http://www.leptonica.org/source/version-notes.html DESCRIPTION

[ANNOUNCEMENT] Updated: tesseract-ocr-3.04.00-3

Version 3.04.00-3 of packages libtesseract-ocr_3 tesseract-ocr tesseract-ocr-devel tesseract-training-util are available in the Cygwin distribution: Other language specific data are available upstream https://github.com/tesseract-ocr/tessdata while training data for building

[ANNOUNCEMENT] Updated: leptonica-1.72-2

Version 1.72-2 of packages leptonica libleptonica-devel libleptonica_3 are available in the Cygwin distribution: CYGWIN CHANGES Modified tmp default dir settings that impacted tesseract training script. CHANGES http://www.leptonica.org/source/version-notes.html DESCRIPTION

Re: Crash X11 with 3 commands

W7-64 for me as well. Same xterm version too. I was on xorg-server 1.17.4-1, but just now upped that to 1.18.0-1 and I'm still getting the crash. Will try upgrading cygwin core as well. On Fri, Dec 11, 2015 at 11:59 AM, Marco Atzeri wrote: > On 11/12/2015 18:54, Jim

Re: Crash X11 with 3 commands

Nope. Still crashing with 2.4.0-0.9 for me. Marco - when you run that script, does your xterm at least iconize? What's in your xterm after you run the script? On Fri, Dec 11, 2015 at 12:47 PM, Nem W Schlecht wrote: > W7-64 for me as well. Same xterm version too. > > I was