black console boxes still a problem for Windows 7 and X?

I just noticed one of those annoying black boxes when running X on Windows 7. I don't think I ever tried to run X there before. The first release of Cygwin which was supposed to fix this problem was 1.7.0-51 but I can't even run X with that version. Have the console windows always been showing u

Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-56

On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote: >On 01/08/2009 15:10, Christopher Faylor wrote: >> I have uploaded a new Cygwin 1.7 test release, 1.7.0-56. >> >> This fixes the bug introduced in -53 and -54 which resulted in various >> problems execing programs as seen here: > >I

Re: [1.7] Updated: cygwin-1.7.0-56

On Mon, Aug 03, 2009 at 11:42:40PM -0400, Christopher Faylor wrote: >On Mon, Aug 03, 2009 at 09:21:35PM -0600, Jim Reisert AD1C wrote: >>I removed the *56* release file from my Cygwin install directory and >>tried a re-install. Now in a DOS window, when I try to start TCSH, I >>get: >> >>f:\>tcsh

Re: $DISPLAY variable empty after SSHing

mcoughlin wrote: Well it is good to know that it is doable. My computer is running Windows Vista, the middle computer runs Red Hat 3, and the work computer runs Red Hat 4. ssh -X computer #2 Warning: untrusted X11 forwarding setup failed: xauth key data not generated Warning: No xauth da

Re: $DISPLAY variable empty after SSHing

Well it is good to know that it is doable. My computer is running Windows Vista, the middle computer runs Red Hat 3, and the work computer runs Red Hat 4. Larry Hall (Cygwin) wrote: > > On 08/03/2009 09:39 PM, mcoughlin wrote: >> >> This may be confusing because I have to SSH twice to reach t

Re: [1.7] Updated: cygwin-1.7.0-56

On 08/03/2009 11:42 PM, Christopher Faylor wrote: On Mon, Aug 03, 2009 at 09:21:35PM -0600, Jim Reisert AD1C wrote: I removed the *56* release file from my Cygwin install directory and tried a re-install. Now in a DOS window, when I try to start TCSH, I get: f:\>tcsh 3 [main] tcsh 6028 _

Re: $DISPLAY variable empty after SSHing

On 08/03/2009 09:39 PM, mcoughlin wrote: This may be confusing because I have to SSH twice to reach the computer I work on. On my home computer, I begin by starting the X server. I run the command: bash-3.2$ echo $DISPLAY :0.0 And so it seems to be working fine. I then do: ssh -X computer #2

Re: [1.7] Updated: cygwin-1.7.0-56

On Mon, Aug 03, 2009 at 09:21:35PM -0600, Jim Reisert AD1C wrote: >I removed the *56* release file from my Cygwin install directory and >tried a re-install. Now in a DOS window, when I try to start TCSH, I >get: > >f:\>tcsh > 3 [main] tcsh 6028 _cygtls::handle_exceptions: Exception: >STATUS_A

Re: [1.7] Updated: cygwin-1.7.0-56

On Tue, Aug 04, 2009 at 11:24:40AM +0800, Huang Bambo wrote: >Try release 51, it's the last stable version for me. Yes. We got that. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Uns

Re: [1.7] Updated: cygwin-1.7.0-56

On Tue, Aug 04, 2009 at 11:21:21AM +0800, Huang Bambo wrote: >I confirm this problem. >After ls command can't list anything, command "strace ls" will work >with correct result. You really do need to check out http://cygwin.com/problems.html . In particular, the cygcheck output mentioned there wou

Re: [1.7] Updated: cygwin-1.7.0-56

Try release 51, it's the last stable version for me. 2009/8/4 Jim Reisert AD1C : > I removed the *56* release file from my Cygwin install directory and > tried a re-install.  Now in a DOS window, when I try to start TCSH, I > get: > > f:\>tcsh >      3 [main] tcsh 6028 _cygtls::handle_exceptions:

Re: [1.7] Updated: cygwin-1.7.0-56

I removed the *56* release file from my Cygwin install directory and tried a re-install. Now in a DOS window, when I try to start TCSH, I get: f:\>tcsh 3 [main] tcsh 6028 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 502 [main] tcsh 6028 open_stackdumpfile: Dumping stac

Re: [1.7] Updated: cygwin-1.7.0-56

I confirm this problem. After ls command can't list anything, command "strace ls" will work with correct result. 2009/8/4 Jim Reisert AD1C : > I did NOT have the problem on my work PC.  I do have the problem on my > home PC (even after rebooting).  Home is running Wnidows SP3, work is > running Wi

Re: [1.7] Updated: cygwin-1.7.0-56

I did NOT have the problem on my work PC. I do have the problem on my home PC (even after rebooting). Home is running Wnidows SP3, work is running Windows SP2 (I think). - Jim On Sun, Aug 2, 2009 at 9:45 AM, Jim Reisert AD1C wrote: > It's worse than that. > > In an xterm, the first "ls" works (

Re: $DISPLAY variable empty after SSHing

In /etc/ssh/ssh_config ForwardX11Trusted yes Is that what you mean? Because that is how it is set currently (that file is on the "in between" computer). Michael Huang Bambo wrote: > > You must have you ssh tool make X forward enabled. > > 2009/8/4 mcoughlin : >> >> This may be confusing bec

Re: $DISPLAY variable empty after SSHing

You must have you ssh tool make X forward enabled. 2009/8/4 mcoughlin : > > This may be confusing because I have to SSH twice to reach the computer I > work on. > > On my home computer, I begin by starting the X server. I run the command: > > bash-3.2$ echo $DISPLAY > :0.0 > > And so it seems to b

$DISPLAY variable empty after SSHing

This may be confusing because I have to SSH twice to reach the computer I work on. On my home computer, I begin by starting the X server. I run the command: bash-3.2$ echo $DISPLAY :0.0 And so it seems to be working fine. I then do: ssh -X computer #2 Warning: untrusted X11 forwarding setup

RE: running MS link.exe under Cygwin sshd?

> From: reply-to-list-only...@cygwin.com > On 08/03/2009 12:11 AM, Jay K wrote: >> I found that Interix sshd and WinSSHD work ok here. >> So it is something specific to Cygwin. > Are you talking about password or public key authentication? If the > latter, Have you tried the LSA authentication pa

RE: running MS link.exe under Cygwin sshd?

Friend also found freesshd works and will use that. So 3 out of 4 sshd work, Cygwin sshd is the only one that doesn't. - Jay [snip] -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation

Re: Flex issues in Cygwin 1.7

On Tue, Aug 04, 2009 at 09:29:23AM +1000, bog gob wrote: >I found an issue with flex while building doxygen-1.5.9 in cygwin 1.7. >One obvious issue is that there is a newline inserted after every >normal line in the .cpp output file, this will break code that needs >multiple lines (like a multi lin

Flex issues in Cygwin 1.7

I found an issue with flex while building doxygen-1.5.9 in cygwin 1.7. One obvious issue is that there is a newline inserted after every normal line in the .cpp output file, this will break code that needs multiple lines (like a multi line macro). The version of flex is 2.5.35 the same version I ha

Re: best way to get sshd to re-read its configuration

cygrunsrv --stop sshd ; cygrunsrv --start sshd cheers, DaveK -- 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

Re: running MS link.exe under Cygwin sshd?

On 08/03/2009 12:11 AM, Jay K wrote: I found that Interix sshd and WinSSHD work ok here. So it is something specific to Cygwin. Are you talking about password or public key authentication? If the latter, Have you tried the LSA authentication package in Cygwin 1.7?

Re: putc_unlocked stdio error when compiling class with mingw32-make

I am trying to compile a huge collection of old code libraries originally written for linux/unix (it manipulates genomic data) for windows using cygwin/mingw32-make and have been successful up to  the last stage where I am getting the following error in class chromAnn. >> chromAnn.c: In function `

Re: stunnel windows x64

On Mon, Aug 03, 2009 at 09:05:04AM -0400, Andrew Schulman wrote: >On Monday 03 August 2009 08:33:44 Tomas Ulicky wrote: >>Hi, it is possible to start releasing pure x64 version of stunnel? >>OpenSSL exist in x64 version and there is gcc that can create x64 >>binaries. It will be good to have one,

Re: Setup maximizing package explorer

On Mon, Aug 03, 2009 at 10:19:02AM -0400, Carl Friedberg wrote: >Christopher, >>The next version of setup.exe will remember what size you choose for >>this window so, if you don't like the way it works now, it will be a >>one-time decision to resize it. > > >Thank you for this. Perhaps you could s

Re: Setup maximizing package explorer

Christopher Faylor wrote: On Mon, Aug 03, 2009 at 10:38:17AM +0300, Arne Pajunen wrote: It is also an inconvenience to have to maximize or otherwise modify the size of the window every single time you need it. Don't assume that your needs are the norm. The next version of setup.exe will remembe

Re: Setup maximizing package explorer

Christopher, > The next version of setup.exe will remember what size you choose for this > window so, if you don't like the way it works now, it will be a one-time > decision to resize it. Thank you for this. Perhaps you could show the release date of net setup on the same line as the version is

Re: stunnel windows x64

On Monday 03 August 2009 08:33:44 Tomas Ulicky wrote: > Hi, it is possible to start releasing pure x64 version of stunnel? > OpenSSL exist in x64 version and there is gcc that can create x64 > binaries. It will be good to have one, because in Windows 2008 R2 server > there will be uninstallable sup

Re: Setup maximizing package explorer

On Mon, Aug 03, 2009 at 10:38:17AM +0300, Arne Pajunen wrote: >I've been using the 1.7 releases and they're quite nice. However, I've >been noticing a minor inconvenience with the new setup: It maximizes to >fullscreen when entering the package explorer. I'm sure this is a nice >feature on small

Re: !! results in -bash: syntax error near unexpected token `newline'

Hi Mark, >> Running "!!" or "!" gives me this: >> -bash: syntax error near unexpected token `newline' > > I'm assuming that the previous command you're trying to repeat worked > the first time with no such syntax error... Yeah, sorry - you are right. I tricked myself there! After a while I found

Re: !! results in -bash: syntax error near unexpected token `newline'

On Sun, Aug 2, 2009 at 9:40 PM, Robert Mark Bram wrote: > Running "!!"  or "!" gives me this: > -bash: syntax error near unexpected token `newline' > > Any ideas what I can do about it? For starters, read http://cygwin.com/problems.html and follow the advice there; we need more information to help

Setup maximizing package explorer

Hey, I've been using the 1.7 releases and they're quite nice. However, I've been noticing a minor inconvenience with the new setup: It maximizes to fullscreen when entering the package explorer. I'm sure this is a nice feature on smaller monitors where people often run programs maximized, but