Re: checkX problems

2009-11-12 Thread Lothar Brendel
Charles Wilson wrote: [...] run.exe is peculiar. The first argument is the target, and IF the VERY NEXT argument is "-wait", run "usurps" that argument. That is, run will invoke: checkX and checkX will never see "-wait". So, what does run.exe do with "-wait"? It...waits. run.exe won't ex

Re: 'run xterm' fails to open a window

2009-11-12 Thread Ken Brown
On 11/12/2009 3:17 PM, Jon TURNEY wrote: On 10/11/2009 23:44, Mike Ayers wrote: On Behalf Of jean-luc malet Sent: Monday, November 09, 2009 2:50 AM no more result... gvim process is still started, appears in ps -a, but nothing is displayed on screen, replacing gvim by xterm still work with th

Re: checkX problems

2009-11-12 Thread Ken Brown
On 11/12/2009 4:31 PM, Jon TURNEY wrote: On 30/10/2009 13:48, Ken Brown wrote: 2. If I start the X server by using the default startxwin.bat or startxwin.sh (both of which call checkX), the server is very unstable and crashes within a few minutes. This happens consistently, and it never happens

Re: checkX problems

2009-11-12 Thread Charles Wilson
Jon TURNEY wrote: > But why would you fix the timeout problem by doing some horrible > horrible iteration in the DOS batch script (horrible) (which would > probably have to busy-wait (also horrible) as there's no sleep command), > when you can fix checkX, which has the bonus of fixing other uses of

RE: Cygwin/x window no longer appears

2009-11-12 Thread Mike Ayers
> If you read the cygcheck output which Olivia kindly provided, you will > see > that she is running cygwin 1.5, with Xserver 1.5.3, so these recent > breakages > relating to Xserver 1.7.1 are unlikely to be the cause of her problems. > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer

Re: checkX problems

2009-11-12 Thread Jon TURNEY
On 12/11/2009 23:09, Lothar Brendel wrote: Jon TURNEY wrote: [...] Fortunately, the X server binds it's socket pretty early in the startup, so this probably works pretty well, but in theory at least there is still a possible timing window in startxwin.bat. Yep, and in my setup the X server *

Re: Cygwin/x window no longer appears

2009-11-12 Thread Jon TURNEY
On 12/11/2009 23:04, Mike Ayers wrote: From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Olivia Cheronet Sent: Thursday, November 12, 2009 2:16 PM I have recently started to work with Cygwin/X. Until now, I have been starting Cygwin/X by using startxwin.b

RE: Cygwin/x window no longer appears

2009-11-12 Thread Mike Ayers
> From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- > ow...@cygwin.com] On Behalf Of Olivia Cheronet > Sent: Thursday, November 12, 2009 2:16 PM > I have recently started to work with Cygwin/X. > Until now, I have been starting Cygwin/X by using startxwin.bat in the > Cygwin bash shell. Ev

Re: checkX problems

2009-11-12 Thread Lothar Brendel
Jon TURNEY wrote: [...] Fortunately, the X server binds it's socket pretty early in the startup, so this probably works pretty well, but in theory at least there is still a possible timing window in startxwin.bat. Yep, and in my setup the X server *always* comes up too late. So it perhaps

Re: Cygwin/x window no longer appears

2009-11-12 Thread Olivia Cheronet
Here is my cygcheck.out. Sorry about that! - Original Message > From: Olivia Cheronet > To: cygwin-xfree@cygwin.com > Sent: Thu, November 12, 2009 10:16:16 PM > Subject: Cygwin/x window no longer appears > > Hello! > > > I have recently started to work with Cygwin/X. > Until now, I

Cygwin/x window no longer appears

2009-11-12 Thread Olivia Cheronet
Hello! I have recently started to work with Cygwin/X. Until now, I have been starting Cygwin/X by using startxwin.bat in the Cygwin bash shell. Everything seemed to be working fine. However, it has now stopped working... When I type "startxwin.bat" in the Cygwin shell, the normal >startxwin.ba

Re: checkX problems

2009-11-12 Thread Jon TURNEY
On 30/10/2009 13:48, Ken Brown wrote: I'm having trouble with checkX. I haven't seen other people complain about this, so I assume it's something about my system, but I can't figure out what. There are two symptoms: 1. If I run checkX with a timeout, the timeout seems to be ignored. For example

Re: Cut & Paste problem between X windows

2009-11-12 Thread Gery
Sounds weird, perhaps you've tried already but did you just highlight the word in the xterm (without clicking) to copy it and then (in some other place) press the middle (button 2) to paste it?I saw some friends having this little problem time ago. Sent from my iPod On Nov 12, 2009, at 3:1

Re: Cut & Paste problem between X windows

2009-11-12 Thread Eliot Moss
dbl...@comcast.net wrote: Hi, I just discovered that setting "LANG=en_US.UTF-8" in my environment solved the problem with pasting into an xterm. Not exactly sure why this fixed that problem, anybody know? I still have the problem with clipboard sharing between windows and cygwinx, though.

RE: 'run xterm' fails to open a window

2009-11-12 Thread Mike Ayers
> From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- > ow...@cygwin.com] On Behalf Of Jon TURNEY > Wait, are you saying that the process that run starts is blocked if it > tries > to output anything? That is what I am experiencing. > Also, the suggestions that this has something t

Re: Cut & Paste problem between X windows

2009-11-12 Thread dblevi
Hi, I just discovered that setting "LANG=en_US.UTF-8" in my environment solved the problem with pasting into an xterm. Not exactly sure why this fixed that problem, anybody know? I still have the problem with clipboard sharing between windows and cygwinx, though. Could this also be related t

Re: 'run xterm' fails to open a window

2009-11-12 Thread Jon TURNEY
On 10/11/2009 23:44, Mike Ayers wrote: On Behalf Of jean-luc malet Sent: Monday, November 09, 2009 2:50 AM no more result... gvim process is still started, appears in ps -a, but nothing is displayed on screen, replacing gvim by xterm still work with this solution... To find out why t

Re: Cut & Paste problem between X windows

2009-11-12 Thread dblevi
Hi, I am having trouble with pasting text into xterm windows, in cygwin1.7. The problem I'm having seems like the same one recently reported in this thread 'Cut & Paste problem between X windows'. However, I am using a microsoft mouse (the problem in that thread was with a logitech mouse). I w

Re: Can't read lock file

2009-11-12 Thread Larry Hall (Cygwin X)
On 11/12/2009 01:16 PM, Jon TURNEY wrote: The only use of the lock file appears to be to stop people from doing things like starting 'X :0 -nolisten inet -nolisten inet6' and 'X :0 -nolisten unix' at the same time, so I'm kind of tempted just to make '-nolock' the default and let people run with

[ANNOUNCEMENT] [1.7] Updated: libX11-1.3.2-2

2009-11-12 Thread Yaakov (Cygwin/X)
The following packages have been updated for Cygwin 1.7: * libX11_6-1.3.2-2 * libX11-devel-1.3.2-2 * libX11-xcb1-1.3.2-2 * libX11-xcb-devel-1.3.2-2 libX11, aka Xlib, is the core library of the X11 protocol. This release adds support for the C.UTF-8 locale. Yaakov Cygwin/X CYGWIN-XFREE-ANNOU

[ANNOUNCEMENT] [1.7] Updated: xorg-server-1.7.1-3

2009-11-12 Thread Yaakov (Cygwin/X)
The following package has been updated for Cygwin 1.7: * xorg-server-1.7.1-3 This package contains XWin and the other X.Org X11 servers. The following patches has been added in this release: - Don't crash if conversion of window name to UTF-8 fails. - Discourage other window managers from star

Re: Can't read lock file

2009-11-12 Thread Jon TURNEY
On 11/11/2009 10:07, Corinna Vinschen wrote: On Nov 11 07:40, Fergus wrote: Q1. Is it still the case that this problem is "not well understood" as in this reference? http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file Hardlinks don't work on FAT filesystems since FAT doesn

Re: Can't read lock file

2009-11-12 Thread Jon TURNEY
On 11/11/2009 07:40, Fergus wrote: I have made no alterations/ patches/ amendments and have a completely current [1.7] system. For all of cygwin1.7.61.dll - cygwin1.7.64.dll the command run XWin fails with a reference to /vat/log/XWin.0.log which reads Can't read lock file /tmp/.X0.lock But whe

Re: cygwin 1.7.0-63 problems with X programs

2009-11-12 Thread Eliot Moss
Thanks, Jon! Installing the three font collections you suggested seems to have solved all THREE of the problems I mentioned. I can only guess that somehow the font/locale issues prevented some .Xdefault information from being loaded or used properly, but I attach the .Xdefaults file anyway. The

Re: Option to disable PRIMARY clipboard

2009-11-12 Thread Corentin Chary
On Thu, Nov 12, 2009 at 2:53 PM, Jon TURNEY wrote: > On 09/11/2009 16:48, Corentin Chary wrote: >> >> Is there a way to disable the PRIMARY clipboard ? >> Would a patch like that >> http://sourceware.org/ml/cygwin-xfree/2003-06/msg00148.html (with a >> command line option) be accepted ? > > It's f

Re: Option to disable PRIMARY clipboard

2009-11-12 Thread Jon TURNEY
On 09/11/2009 16:48, Corentin Chary wrote: Is there a way to disable the PRIMARY clipboard ? Would a patch like that http://sourceware.org/ml/cygwin-xfree/2003-06/msg00148.html (with a command line option) be accepted ? It's far more likely to be accepted if you say what problem you are trying

Re: cygwin 1.7.0-63 problems with X programs

2009-11-12 Thread Jon TURNEY
On 08/11/2009 14:11, Eliot Moss wrote: Corinna Vinschen wrote: On Nov 7 09:27, Eliot Moss wrote: Like another user, I had difficulty getting X to fire up. After setting LANG=en_US.UTF-8 I got farther, but these issues remain: Each xterm, xemacs, and xclock I start outputs this: Warning: Missi

Re: building issue

2009-11-12 Thread Jon TURNEY
On 07/11/2009 01:10, Cesar Strauss wrote: Jon TURNEY wrote: I think I've finally found out why these "Permission denied" errors occur. It seems to be caused by the XWin.exe.manifest file we store in the same directory (it's not shipped as it's embedded into the final executable using the resour

WM_QUIT problem (was "twm issue ...")

2009-11-12 Thread Eliot Moss
Since nobody has responded at all, I thought I would try again, a different way ... This is a case where what I believe is normal termination of a window manager (in my case twm) is causing a seg fault in XWin, at least that's what the attached log seems to say. The odd thing is that this happen