From jamesem_99@yahoo.com Mon May 2 12:33:00 2011 From: jamesem_99@yahoo.com (James Merritt) Date: Mon, 02 May 2011 12:33:00 -0000 Subject: No subject Message-ID: <181560.31228.qm@web121416.mail.ne1.yahoo.com> .Cigarettes are only for losers! http://auxilingua.org/page.php?mehotmailID=07w4 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jamesem_99@yahoo.com Mon May 2 14:17:00 2011 From: jamesem_99@yahoo.com (James Merritt) Date: Mon, 02 May 2011 14:17:00 -0000 Subject: No subject Message-ID: <181560.31228.qm@web121416.mail.ne1.yahoo.com> .Cigarettes are only for losers! http://auxilingua.org/page.php?mehotmailID=07w4 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From ryanjohn@ece.cmu.edu Sat May 7 11:51:00 2011 From: ryanjohn@ece.cmu.edu (Ryan Johnson) Date: Sat, 07 May 2011 11:51:00 -0000 Subject: Still can't run XServer or any apps that require it In-Reply-To: <4DB96AC4.5000905@dronecode.org.uk> References: <4DB96AC4.5000905@dronecode.org.uk> Message-ID: <4DBEBCDE.10001@ece.cmu.edu> On 2:59 PM, Jon TURNEY wrote: > Looking into this a bit more, it's not quite clear what's going on here: > > There's a few failure modes which can be reported as "XKB: Could not invoke > xkbcomp", but the assumption that this is a fork() failure seems likely, given > that the problem can be made to go away by rebasing. > > But I think that, at the point which fork() is invoked, XWin hasn't loaded any > DLLs yet, so the fork() failure shouldn't be due to an inability to remap DLLs > in the child to the same address as the parent. The address space layout randomization feature as implemented in Win7-x64 (and probably Vista/x86 as well) means that *any* dll can fail to map to the same address as its parent. Often it's the parent that's messed up, which means no subsequent fork() is likely to succeed. That's why the problem comes in spurts: if you get a good parent, where nothing got pushed around the wrong way, fork() will eventually succeed thanks to Win7's feature which restarts crashed processes automatically (essentially retrying the fork until a "good" child arrives). If you get a bad parent, though, the chances of getting a compatibly bad child are pretty low. I see this a lot in emacs; Windows usually gives up after 5-6 crashes in a row. Enabling the tsaware bit for every dll should also help (see docs for peflagsall), because Windows will at least do its best to not clobber any dll with any other dll, but it still doesn't prevent a random thread stack or heap placement from pushing a dll out of its way. >>>>> [1] http://cygwin.com/snapshots/ >>>> Also, I've found that using a different base address with rebaseall >>>> seems to help with some X problems: >>>> >>>> dash -c "rebaseall -b 0x77000000" >>>> >>>> http://cygwin.com/ml/cygwin/2011-04/msg00306.html >>>> >>> Ok, that appears to have fixed my problem. Is that a "permanent" fix? >> For now, yes. ;-) > Humour-impaired persons, please note smiley AFAICT, that's actually a 100% accurate description of rebaseall. The "fix"will last until the next time Windows hands you a badly laid-out parent process (transient problem, just restart the parent), or until the next run of cygwin setup replaces rebased dlls with newer-but-not-rebased versions (permanent, have to re-rebaseall). Ryan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From schweikh@schweikhardt.net Wed May 11 17:40:00 2011 From: schweikh@schweikhardt.net (Jens Schweikhardt) Date: Wed, 11 May 2011 17:40:00 -0000 Subject: xterm update Message-ID: <20110507115125.GD49291@schweikhardt.net> Jon et al., cygwin/x still ships with xterm 261 as of June last year. I'm eagerly expecting an update to xterm 270 which I hope includes the fix for the scrollbar drawing issue with the solution as discussed in http://www.mail-archive.com/cygwin-xfree%40cygwin.com/msg20551.html Is some other issue getting in the way of updating/fixing xterm or is it simply ENOTIME? :-) Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From whatzit_toya@mail.com Sun May 15 08:36:00 2011 From: whatzit_toya@mail.com (Whatzit Toya) Date: Sun, 15 May 2011 08:36:00 -0000 Subject: frequently getting a =?utf-8?b?U1RBVFVTX0FDQ0VTU19WSU9MQVRJT04=?= exception under win7 References: Message-ID: I was having this same issue running WIN7 x64, cygwin1.dll version 1.7.9, and no Security Essentials or any other a/v software. This is how I fixed the issue: I went into my cygwin installation folder (C:\cygwin\bin), right clicked on "sh.exe", selected "Properties", selected the "Compatibility" tab, and checked "Run this program as an administrator". I did the same thing for "bash.exe". Now it works beautifully without any error messages. Hope this helps. PS On "sh.exe" I also have it running in compatibility mode for Win XP SP2 but I don't think it is necessary. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From avnewsl9@gmail.com Tue May 17 22:47:00 2011 From: avnewsl9@gmail.com (AZ White) Date: Tue, 17 May 2011 22:47:00 -0000 Subject: Perche' aspettare? Message-ID: <20110515103603.FTCFINNSYSKYLU@gmail.com> Ora puoi avere denti bianchissimi subito con il nuovo sbiancante per denti rapido. Risultato visibile da subito e duraturo. Cliccare su: http://dentibianchi.visit-page.com Azienda e garanzia Italiana! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From Life.Options@introduceastride.com Wed May 18 17:16:00 2011 From: Life.Options@introduceastride.com (Life Options) Date: Wed, 18 May 2011 17:16:00 -0000 Subject: 250k Policies for a $1. In-Reply-To: cygwin-xfree@cygwin.com Message-ID: <1305672432.qomfoeqdasv@introduceastride.com> Protect Your Wife and Kids, Even when you're Not around We can Help you, get the best Life Options Here, http://rowles.introduceastride.com/1462530y124h1256731 We all know how stressful that can be, make sure you are prepared. Right 450 Ocean ave #b Laguna Beach CA 92651 To stop go here, http://rowles.introduceastride.com/1462531y124h1256731 to leave: http://introduceastride.com/?e=cygwin-xfree@cygwin.com or post: PO Box 10188 Room #55, Newark, NJ, 07101-3188, US -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jgrierson@churchbudget.com Wed May 18 19:27:00 2011 From: jgrierson@churchbudget.com (Jon Grierson @ Church Budget) Date: Wed, 18 May 2011 19:27:00 -0000 Subject: Nautilus Message-ID: <4DD3FEE7.1000709@churchbudget.com> I have install nautilus into my cygwin enviroment and depending upon the version I install I get an error abgout a missing dll. With install version 2.24.2-1 I get the error cygeel-2.2.dll is missing. With install version 2.32.1-1 I get the error cygunique-1.0-0.dll is missing. I cannpt fond either dll anywhere. The suggestion to install gnome translate is a problem as I cannot find this package anywhere either. Once nautilus is running I can use my new shiny cygwin environment for lots of chores. Cheers Jon G -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From marco.atzeri@gmail.com Thu May 19 15:35:00 2011 From: marco.atzeri@gmail.com (marco atzeri) Date: Thu, 19 May 2011 15:35:00 -0000 Subject: Nautilus In-Reply-To: <4DD3FEE7.1000709@churchbudget.com> References: <4DD3FEE7.1000709@churchbudget.com> Message-ID: On Wed, May 18, 2011 at 7:16 PM, Jon Grierson @ Church Budget wrote: > I have install nautilus into my cygwin enviroment and depending upon the > version I install I get an error abgout a missing dll. ?With install version > 2.24.2-1 I get the error cygeel-2.2.dll is missing. ?With install version > 2.32.1-1 I get the error cygunique-1.0-0.dll is missing. ?I cannpt fond > either dll anywhere. ?The suggestion to install ?gnome translate is a > problem as I cannot find this package anywhere either. Once nautilus is > running I can use my new shiny cygwin environment for lots of chores. > > Cheers > Jon G Nautilus is not in cygwin packages. I guess you installed from http://sourceware.org/cygwinports/ so you should ask support there. Regards Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dfelicia@donsbox.com Thu May 19 22:18:00 2011 From: dfelicia@donsbox.com (webmaster) Date: Thu, 19 May 2011 22:18:00 -0000 Subject: xterm update In-Reply-To: <20110507115125.GD49291@schweikhardt.net> References: <20110507115125.GD49291@schweikhardt.net> Message-ID: > I'm eagerly expecting an update to xterm 270 which I hope includes the > fix for the scrollbar drawing issue You can get 269 from git: http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/xterm;a=summary To build 270 just modify the 269 .cygport. When I build 269 or 270 the scrollbar issue is fixed, but this line in my ~/.Xdefaults stops having an effect: *VT100*faceName: Terminus:pixelsize=12:antialias=true XTerm 261 has the scrollbar issue, but I get my nice Terminus font. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dickey@his.com Fri May 20 01:29:00 2011 From: dickey@his.com (Thomas Dickey) Date: Fri, 20 May 2011 01:29:00 -0000 Subject: xterm update In-Reply-To: References: <20110507115125.GD49291@schweikhardt.net> Message-ID: <20110519181415.U70528@mail101.his.com> On Thu, 19 May 2011, webmaster wrote: >> I'm eagerly expecting an update to xterm 270 which I hope includes the >> fix for the scrollbar drawing issue > You can get 269 from git: > http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/xterm;a=summary > > To build 270 just modify the 269 .cygport. > > When I build 269 or 270 the scrollbar issue is fixed, but this line in > my ~/.Xdefaults stops having an effect: perhaps your development environment lacks the FreeType library (that would show up in the configure step) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dfelicia@donsbox.com Fri May 20 08:34:00 2011 From: dfelicia@donsbox.com (webmaster) Date: Fri, 20 May 2011 08:34:00 -0000 Subject: xterm update In-Reply-To: <20110519181415.U70528@mail101.his.com> References: <20110507115125.GD49291@schweikhardt.net> <20110519181415.U70528@mail101.his.com> Message-ID: > perhaps your development environment lacks the FreeType library > (that would show up in the configure step) Ah, indeed. Thanks! For anyone who can't wait for xterm > 261 to be included, here's version 270: http://www.donsbox.com/~dfelicia/xterm-270-1.tar.bz2 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From haba713@gmail.com Tue May 24 19:32:00 2011 From: haba713@gmail.com (Harri T.) Date: Tue, 24 May 2011 19:32:00 -0000 Subject: Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. Message-ID: <4DD6276D.3030801@gmail.com> Hi! My Cygwin/X fails to start. /var/log/xwin/XWin.0.log: > [ 667.715] (EE) XKB: Could not invoke xkbcomp > [ 667.715] (EE) XKB: Couldn't compile keymap > [ 667.715] (EE) XKB: Failed to load keymap. Loading default keymap instead. > [ 669.571] (EE) XKB: Could not invoke xkbcomp > [ 669.571] (EE) XKB: Couldn't compile keymap > [ 669.571] XKB: Failed to compile keymap > [ 669.571] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. > [ 669.571] > Fatal server error: > [ 669.571] Failed to activate core devices. Full /var/log/xwin/XWin.0.log is here (expires in 7 days): http://pastebin.com/80rjKMwb At first X used to work well. Then problems started when I didn't log in Windows immediately when login prompt appeared. Now I can't start X at all. "cygcheck xkbcomp" finds no failures in library loading and "rebaseall" does not help. Any idea? Harri -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Wed May 25 14:54:00 2011 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 25 May 2011 14:54:00 -0000 Subject: Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. In-Reply-To: <4DD6276D.3030801@gmail.com> References: <4DD6276D.3030801@gmail.com> Message-ID: <4DDC0807.4030603@dronecode.org.uk> On 20/05/2011 09:33, Harri T. wrote: > Hi! My Cygwin/X fails to start. > > /var/log/xwin/XWin.0.log: >> [ 667.715] (EE) XKB: Could not invoke xkbcomp >> [ 667.715] (EE) XKB: Couldn't compile keymap >> [ 667.715] (EE) XKB: Failed to load keymap. Loading default keymap instead. >> [ 669.571] (EE) XKB: Could not invoke xkbcomp >> [ 669.571] (EE) XKB: Couldn't compile keymap >> [ 669.571] XKB: Failed to compile keymap >> [ 669.571] Keyboard initialization failed. This could be a missing or >> incorrect setup of xkeyboard-config. >> [ 669.571] >> Fatal server error: >> [ 669.571] Failed to activate core devices. > > Full /var/log/xwin/XWin.0.log is here (expires in 7 days): > http://pastebin.com/80rjKMwb > > At first X used to work well. Then problems started when I didn't log in > Windows immediately when login prompt appeared. Now I can't start X at all. > > "cygcheck xkbcomp" finds no failures in library loading and "rebaseall" does > not help. > > Any idea? Unfortunately, rebaseall is a rather limited workaround, rather than a solution for these issues (for reasons which have been discussed extensively in the past) I've been considering, as a temporary solution, changing the XWin server to use system() rather than pipe() & fork() to invoke xkbcomp, which should work around this problem until the upstream X server changes to using libxkbcommon, which will avoid the need to run xkbcomp entirely. (Although I imagine this will just transform the problem reports from "I can't start the X server" (as it can't successfully fork() xkbcomp) to "I can't start anything from the X server traymenu" (as it can't successfully fork() those programs) I've build a snapshot with this change and uploaded it at [1], perhaps you could try that out and see if that makes a difference for you. (Since this snapshot is based on RC2 for the forthcoming 1.10.2 release, it also contains some upstream GLX changes which might break GLX on XWin which I haven't had a chance to test yet) [1] ftp://cygwin.com/pub/cygwinx/XWin.20110524-git-3b1bff1452ba8e19.exe.bz2 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dk068x@att.com Fri May 27 00:50:00 2011 From: dk068x@att.com (KARR, DAVID (ATTSI)) Date: Fri, 27 May 2011 00:50:00 -0000 Subject: Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. In-Reply-To: <4DD6276D.3030801@gmail.com> References: <4DD6276D.3030801@gmail.com> Message-ID: > -----Original Message----- > Subject: Keyboard initialization failed. This could be a missing or > incorrect setup of xkeyboard-config. > > Hi! My Cygwin/X fails to start. > > /var/log/xwin/XWin.0.log: > > [ 667.715] (EE) XKB: Could not invoke xkbcomp > > [ 667.715] (EE) XKB: Couldn't compile keymap > > [ 667.715] (EE) XKB: Failed to load keymap. Loading default > keymap instead. > > [ 669.571] (EE) XKB: Could not invoke xkbcomp > > [ 669.571] (EE) XKB: Couldn't compile keymap > > [ 669.571] XKB: Failed to compile keymap > > [ 669.571] Keyboard initialization failed. This could be a > missing or incorrect setup of xkeyboard-config. > > [ 669.571] > > Fatal server error: > > [ 669.571] Failed to activate core devices. > > Full /var/log/xwin/XWin.0.log is here (expires in 7 days): > http://pastebin.com/80rjKMwb > > At first X used to work well. Then problems started when I didn't log > in Windows immediately when login prompt appeared. Now I can't start X > at all. > > "cygcheck xkbcomp" finds no failures in library loading and "rebaseall" > does not help. Until a better solution comes along, it's been noted in this list that "rebaseall -b 0x77000000" appears to resolve this. It did for me, at least, when a plain "rebaseall" did not work. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From Andrew.DeFaria@tellabs.com Sat May 28 00:00:00 2011 From: Andrew.DeFaria@tellabs.com (Andrew DeFaria) Date: Sat, 28 May 2011 00:00:00 -0000 Subject: Can't talk to X server through ssh tunnel after ~ 18 minutes Message-ID: I ssh from my Cygwin box to a Linux machine (happens with Solaris machines too) and I can run X applications back to Cygwin/X without a problem. However, after a few minutes something happens to the tunnel and I can no longer put up any X windows: $ cat checks.sh #!/bin/bash while true; do date xclock & sleep 2 killall xclock if [ $? != 0 ]; then echo Cannot talk to X Server anymore else sleep 60 fi done $ checkx.sh Tue May 24 09:48:43 PDT 2011 ./checkx.sh: line 12: 10927 Terminated xclock Tue May 24 09:49:45 PDT 2011 ./checkx.sh: line 12: 11393 Terminated xclock Tue May 24 09:50:47 PDT 2011 b./checkx.sh: line 12: 11592 Terminated xclock Tue May 24 09:51:49 PDT 2011 ./checkx.sh: line 12: 11782 Terminated xclock Tue May 24 09:52:51 PDT 2011 ./checkx.sh: line 12: 11977 Terminated xclock Tue May 24 09:53:53 PDT 2011 ./checkx.sh: line 12: 12161 Terminated xclock Tue May 24 09:54:55 PDT 2011 ./checkx.sh: line 12: 12345 Terminated xclock Tue May 24 09:55:57 PDT 2011 ./checkx.sh: line 12: 12534 Terminated xclock Tue May 24 09:56:59 PDT 2011 ./checkx.sh: line 12: 12723 Terminated xclock Tue May 24 09:58:01 PDT 2011 ./checkx.sh: line 12: 12912 Terminated xclock Tue May 24 09:59:03 PDT 2011 ./checkx.sh: line 12: 13142 Terminated xclock Tue May 24 10:00:05 PDT 2011 ./checkx.sh: line 12: 13345 Terminated xclock Tue May 24 10:01:07 PDT 2011 ./checkx.sh: line 12: 13578 Terminated xclock Tue May 24 10:02:09 PDT 2011 ./checkx.sh: line 12: 13843 Terminated xclock Tue May 24 10:03:11 PDT 2011 ./checkx.sh: line 12: 14074 Terminated xclock Tue May 24 10:04:13 PDT 2011 ./checkx.sh: line 12: 14260 Terminated xclock Tue May 24 10:05:16 PDT 2011 ./checkx.sh: line 12: 14455 Terminated xclock Tue May 24 10:06:18 PDT 2011 X connection to localhost:15.0 broken (explicit kill or server shutdown). xclock: no process killed Cannot talk to X Server anymore After this I cannot re-establish an X connection until I exit the ssh session and ssh back in again. Any ideas? (I'm gonna post this to both Cygwin and Cygwin-X as I'm not sure if this is a problem with ssh or a problem with X). -- Andrew DeFaria
If a man says something in the woods and there are no women there, is he still wrong? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jimb@jsbc.cc Sun May 29 23:13:00 2011 From: jimb@jsbc.cc (Jim Burwell) Date: Sun, 29 May 2011 23:13:00 -0000 Subject: Can't talk to X server through ssh tunnel after ~ 18 minutes In-Reply-To: References: Message-ID: <4DE03B27.4010709@jsbc.cc> I have a similar issue on Windows 7 64 bit. I don't even use SSH. I can just run an Xterm or other X app with display pointed directly to the IP (after doing proper xhost, etc), and the window will display (often I'll get crashes and stack traces a few times, then it will display). But then the windows will just vanish for no real reason. The X application will still be running on the remote box, but the window is no where to be found on the display. I typically kill off the xterm on the remote box and run it again. It's like the X server under windows is simply unmapping the window and it goes into never-never land. It happens fairly randomly to random clients running on the same or different hosts. One or two x-app windows will vanish from that host, while others are still running fine. Never happened to me under XP 32 bit. - Jim On 5/25/2011 10:43, Andrew DeFaria wrote: > I ssh from my Cygwin box to a Linux machine (happens with Solaris > machines too) and I can run X applications back to Cygwin/X without a > problem. However, after a few minutes something happens to the tunnel > and I can no longer put up any X windows: > > $ cat checks.sh > #!/bin/bash > while true; do > date > xclock & > sleep 2 > killall xclock > if [ $? != 0 ]; then > echo Cannot talk to X Server anymore > else > sleep 60 > fi > done > $ checkx.sh > Tue May 24 09:48:43 PDT 2011 > ./checkx.sh: line 12: 10927 Terminated xclock > Tue May 24 09:49:45 PDT 2011 > ./checkx.sh: line 12: 11393 Terminated xclock > Tue May 24 09:50:47 PDT 2011 > b./checkx.sh: line 12: 11592 Terminated xclock > Tue May 24 09:51:49 PDT 2011 > ./checkx.sh: line 12: 11782 Terminated xclock > Tue May 24 09:52:51 PDT 2011 > ./checkx.sh: line 12: 11977 Terminated xclock > Tue May 24 09:53:53 PDT 2011 > ./checkx.sh: line 12: 12161 Terminated xclock > Tue May 24 09:54:55 PDT 2011 > ./checkx.sh: line 12: 12345 Terminated xclock > Tue May 24 09:55:57 PDT 2011 > ./checkx.sh: line 12: 12534 Terminated xclock > Tue May 24 09:56:59 PDT 2011 > ./checkx.sh: line 12: 12723 Terminated xclock > Tue May 24 09:58:01 PDT 2011 > ./checkx.sh: line 12: 12912 Terminated xclock > Tue May 24 09:59:03 PDT 2011 > ./checkx.sh: line 12: 13142 Terminated xclock > Tue May 24 10:00:05 PDT 2011 > ./checkx.sh: line 12: 13345 Terminated xclock > Tue May 24 10:01:07 PDT 2011 > ./checkx.sh: line 12: 13578 Terminated xclock > Tue May 24 10:02:09 PDT 2011 > ./checkx.sh: line 12: 13843 Terminated xclock > Tue May 24 10:03:11 PDT 2011 > ./checkx.sh: line 12: 14074 Terminated xclock > Tue May 24 10:04:13 PDT 2011 > ./checkx.sh: line 12: 14260 Terminated xclock > Tue May 24 10:05:16 PDT 2011 > ./checkx.sh: line 12: 14455 Terminated xclock > Tue May 24 10:06:18 PDT 2011 > X connection to localhost:15.0 broken (explicit kill or server shutdown). > xclock: no process killed > Cannot talk to X Server anymore > > After this I cannot re-establish an X connection until I exit the ssh > session and ssh back in again. Any ideas? > > (I'm gonna post this to both Cygwin and Cygwin-X as I'm not sure if > this is a problem with ssh or a problem with X). -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5117 bytes Desc: S/MIME Cryptographic Signature URL: