On Sat, 4 Jan 2020 10:51:42 +0900
Takashi Yano wrote:
> On Thu, 2 Jan 2020 22:16:02 +
> Ken Brown wrote:
> > I think this narrows it down to one of the following commits:
>
> I looked into this probelm and found the issue occurs after
> the following commit.
>
> > commit 915fcd0ae8d83546ce135
On Thu, 2 Jan 2020 22:16:02 +
Ken Brown wrote:
> I think this narrows it down to one of the following commits:
I looked into this probelm and found the issue occurs after
the following commit.
> commit 915fcd0ae8d83546ce135131cd25bf6795d97966
> Author: Takashi Yano
> Date: Thu Sep 5 13:22:
[Please don't top-post on this list.]
On 1/2/2020 4:25 PM, ianpu...@gmail.com wrote:
> Now narrowed down to cygwin1.dll version 3.1.0-0.4 as the release which
> introduced this issue.
>
> I found the intervening versions between 3.0.7-1 and 3.1.0-1 as test
> releases in earlier release archives a
Now narrowed down to cygwin1.dll version 3.1.0-0.4 as the release which
introduced this issue.
I found the intervening versions between 3.0.7-1 and 3.1.0-1 as test
releases in earlier release archives at crouchingtigerhiddenfruitbat.org, so
incrementally installing those from 3.1.0-0.1, I found th
On 1/2/2020 2:16 PM, ianpu...@gmail.com wrote:
> Hi.
>
> I don't know if this will help at all since there is a big time gap and it
> looks like a lot of changes between these, but I tried the cygwin1 dlls from
> the snapshots at https://www.cygwin.com/snapshots and found that the
> 2019-08-19 sna
Hi.
I don't know if this will help at all since there is a big time gap and it
looks like a lot of changes between these, but I tried the cygwin1 dlls from
the snapshots at https://www.cygwin.com/snapshots and found that the
2019-08-19 snapshot works fine, the next one dated 2019-11-03 introduces
The problem is with cygwin 3.1.0-1, released on Dec 16th, or thereabouts.
I decided to track it down by re-installing the earlier working release from
the Cygwin time machine at crouchingtigerhiddenfruitbat.org, and then
incrementally upgrading it until the problem showed up. It turns out that it
On 2019-09-12 07:37, Haanraadts, Mark (HBO) via cygwin wrote:
> I have a problem with remote ssh sessions to corporate Red Hat 6 servers and
> X11 forwarding. Xclock works perfectly fine on my local CYGWIn install. On a
> remote server I get:
> $ xclock
> Error: Can't open display:
>
> Here's th
On 06/18/2013 04:01 PM, Jon TURNEY wrote:
On 18/06/2013 17:23, Andrew DeFaria wrote:
Lately I noticed the following error when attempting to ssh from my Ubuntu
Not sure if "lately" means you haven't changed anything, but it didn't report
this error before, or you've only recently started paying
On 18/06/2013 17:23, Andrew DeFaria wrote:
> Lately I noticed the following error when attempting to ssh from my Ubuntu
Not sure if "lately" means you haven't changed anything, but it didn't report
this error before, or you've only recently started paying attention :D
> (13.04) systems to my Cygw
Hi!
Bitte antworten an [EMAIL PROTECTED]
An: Thomas Schweikle <[EMAIL PROTECTED]>
Kopie: [EMAIL PROTECTED]
Thema: Re: X11 forwarding
On Fri, 4 Oct 2002, Thomas Schweikle wrote:
> X11 forwarding is only initiated if the DISPLAY variable
> is set. Try setting DISPLAY to &q
On Fri, 4 Oct 2002, Thomas Schweikle wrote:
> Hi!
>
> Bitte antworten an [EMAIL PROTECTED]
> An: Thomas Schweikle <[EMAIL PROTECTED]>
> Kopie: [EMAIL PROTECTED]
> Thema: Re: X11 forwarding
>
> > On Thu, 3 Oct 2002, Thomas Schweikle wrote:
> >
> &g
Hi!
Bitte antworten an [EMAIL PROTECTED]
An: Thomas Schweikle <[EMAIL PROTECTED]>
Kopie: [EMAIL PROTECTED]
Thema: Re: X11 forwarding
> On Thu, 3 Oct 2002, Thomas Schweikle wrote:
>
>> Hi!
>> connecting cygwin ssh to a linux box with
>>ssh -X
On Thu, 3 Oct 2002, Thomas Schweikle wrote:
> Hi!
> connecting cygwin ssh to a linux box with
>ssh -X -l user host
> doesn't do X11 forwarding. I am shure it is enabled by sshd on the server
> side. Any clues where I have to look to make it work?
Works for me. Every day, in fact. You're go
14 matches
Mail list logo
