On 30/07/2013 18:33, Jim Reisert AD1C wrote:
I have the latest version of Cygwin (using setup-x86). I see the same
problem on both 32-bit and 64-bit Windows 7 systems.
CYGWIN_NT-6.1 LTDEN-REISERT 1.7.22(0.268/5/3) 2013-07-22 17:06 i686 Cygwin
Here is how I am starting X:
On Wed, Jul 31, 2013 at 5:58 AM, Jon TURNEYwrote:
I can't reproduce this.
Can you try downgrading to run-1.2.0 and see if the problem still exists, that
seems to have caused some people problems [1]
[1] http://cygwin.com/ml/cygwin/2013-07/msg00532.html
Thanks, Jon. Downgrading to
On Wed, Jul 31, 2013 at 7:41 AM, Jim Reisert AD1C wrote:
On Wed, Jul 31, 2013 at 5:58 AM, Jon TURNEYwrote:
I can't reproduce this.
Can you try downgrading to run-1.2.0 and see if the problem still exists,
that
seems to have caused some people problems [1]
[1]
On 7/31/2013 9:41 AM, Jim Reisert AD1C wrote:
[1] http://cygwin.com/ml/cygwin/2013-07/msg00532.html
Yeah, I need to add even more runtime-debugging in run-1.0 and put out a
test release, so we can figure out what's going wrong there.
Is there a way to test run-2.0? What is the syntax to
