Re: xterm doesn't open on start (was: checkX problems)
Christopher Faylor wrote: On Thu, Dec 03, 2009 at 12:25:14AM +0100, Lothar Brendel wrote: More information as promised, after getting the new run and checkX (run2) packages announced this morning. $ checkX -v run2 0.3.2 0.3.2 announced? I didn't get any such message, and setup still only offers 0.3.1-1 to me. http://cygwin.com/ml/cygwin-announce/2009-12/msg2.html http://cygwin.com/ml/cygwin/2009-12/msg00079.html Thanx. I had just focused on cygwin-xfree, but indeed run2 is more general. Ciao Lothar -- 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/
RE: xterm doesn't open on start (was: checkX problems)
More information as promised, after getting the new run and checkX (run2) packages announced this morning. $ checkX -v run2 0.3.2 - QUOTE - Lothar Brendel wrote: Timares, Brian (Patriot) wrote: The X window showed up, but it blew up real good (the windows disappeared, then the X icon. After a rebootit didn't launch at all. I ran startxwin.sh from the Cygwin Bash Shell, and it started. At least we're getting *somewhere* :-) Ok, what happens when entering the two vital commands by hand in the the Cygwin Bash Shell (waiting with the second until the X-icon has appeared)? XWin -multiwin xterm -display :0 Reproducible success? I'll try again from home (I went into the office to simplify things). Here is what I got (sorry for the word-wrap): vhaisbtim...@isb-timaresbrian-lt ~ $ XWin -multiwindow [1] 5004 vhaisbtim...@isb-timaresbrian-lt ~ $ Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 - UNQUOTE - Trying from home with the VPN active, again, it works; here is the ps from the xterm that showed up: vhaisbtim...@isb-timaresbrian-lt ~ $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 3556 13556 35560 180490 11:11:27 /usr/bin/bash 6020 16020 6020? 180490 11:11:28 /usr/bin/ssh-agent I294435562944 36880 180490 11:12:07 /usr/bin/XWin 593635565936 40600 180490 11:12:56 /usr/bin/xterm 478059364780 18401 180490 11:12:57 /usr/bin/bash 9324780 932 46961 180490 11:12:59 /usr/bin/ps After quitting and destroying any processes from a DOS window, trying startxwin.bat with echo on First off all, nothing appeared (no X icon, no window). Here is what ps in a DOS window shows after running startxwin.bat: C:\cygwin\binps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 1656 11656 16560 180490 10:57:45 /usr/bin/bash 5516 15516 5516? 180490 10:57:47 /usr/bin/ssh-agent I467616561656 44760 180490 10:57:47 /usr/bin/ssh-add I2024 12024 20241 180490 11:09:16 /usr/bin/bash 1464 11464 14642 180490 11:09:40 /usr/bin/ps Here is the output with blank lines and REM lines removed (I added the 2nd SET DISPLAY, CYGWIN is set to tty elsewhere as well as here, I don't know what that is at the end of the PATH): C:\cygwin\binstartxwin.bat C:\cygwin\binSET DISPLAY=127.0.0.1:0.0 C:\cygwin\binSET CYGWIN=tty tty tty C:\cygwin\binif defined CYGWIN_ROOT goto :OK C:\cygwin\binSET RUN=C:\cygwin\bin\\..\bin\run -p /usr/bin C:\cygwin\binSET PATH=C:\cygwin\bin\\..\bin;C:\cygwin\bin\\..\bin;C:\WINDOWS\system32;C:\ WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\IBM\Personal Communications\;C:\Program Files\IBM\Trace Facility\;C:\Program Files\Common Files\InterSystems\Cache;C:\Program Files\Windows Imaging\;C:\Program Files\ActivIdentity\ActivClient\;P C:\cygwin\binSET XAPPLRESDIR= C:\cygwin\binSET XCMSDB= C:\cygwin\binSET XKEYSYMDB= C:\cygwin\binSET XNLSPATH= C:\cygwin\binif not exist C:\cygwin\bin\\..\tmp\.X11-unix\X0 goto CLEANUP-FINISH C:\cygwin\binattrib -s C:\cygwin\bin\\..\tmp\.X11-unix\X0 C:\cygwin\bindel C:\cygwin\bin\\..\tmp\.X11-unix\X0 C:\cygwin\binif exist C:\cygwin\bin\\..\tmp\.X11-unix rmdir C:\cygwin\bin\\..\tmp\.X11-unix C:\cygwin\binSET DISPLAY=127.0.0.1:0.0 C:\cygwin\binC:\cygwin\bin\\..\bin\run -p /usr/bin bash -l -c XWin -multiwindow -clipboard -silent-dup-error -winkill -emulate3buttons 100 C:\cygwin\binC:\cygwin\bin\\..\bin\run -p /usr/bin checkX -wait -d 127.0.0.1:0.0 -t 12 C:\cygwin\binC:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e /usr/bin/bash -l C:\cygwin\bin At this point I run Cygwin Bash Shell and from that window I run startxwin.bat and it works fine, even after closing the Cygwin Bash Shell. Brian Timares -- 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/
Re: xterm doesn't open on start (was: checkX problems)
Hi! More information as promised, after getting the new run and checkX (run2) packages announced this morning. $ checkX -v run2 0.3.2 0.3.2 announced? I didn't get any such message, and setup still only offers 0.3.1-1 to me. vhaisbtim...@isb-timaresbrian-lt ~ $ XWin -multiwindow [1] 5004 vhaisbtim...@isb-timaresbrian-lt ~ $ Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 - UNQUOTE - Yes, the log didn't show anything unusual. (BTW: You got it from /var/log/XWin.log.0, not from stdout, right?) After quitting and destroying any processes from a DOS window, trying startxwin.bat with echo on First off all, nothing appeared (no X icon, no window). [...] At this point I run Cygwin Bash Shell and from that window I run startxwin.bat and it works fine, even after closing the Cygwin Bash Shell. Brief, running ``startxwin.bat'' from the Cygwin Bash Shell works while running it from a Windows Prompt (DOS window) does not. Right? Ok, same check over there. In the Windows Prompt: C:\cygwin\bin\run XWin What does happen? Nothing? Asks Lothar -- 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/
Re: xterm doesn't open on start (was: checkX problems)
On Thu, Dec 03, 2009 at 12:25:14AM +0100, Lothar Brendel wrote: More information as promised, after getting the new run and checkX (run2) packages announced this morning. $ checkX -v run2 0.3.2 0.3.2 announced? I didn't get any such message, and setup still only offers 0.3.1-1 to me. http://cygwin.com/ml/cygwin-announce/2009-12/msg2.html http://cygwin.com/ml/cygwin/2009-12/msg00079.html cgf -- 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/
RE: xterm doesn't open on start (was: checkX problems)
Lothar Brendel wrote: Timares, Brian (Patriot) wrote: Just to be clear from the start, Cygwin 1.7 not 1.5. ACK. *blush* Sorry! ... Thus, once more: What does md5sum /usr/bin/checkX yield? a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216? The 2nd: vhaisbtim...@isb-timaresbrian-lt ~ $ md5sum /usr/bin/checkX a36409714f5ce9d01e8dfb4cb38b7216 */usr/bin/checkX $ checkX -v run2 0.3.0 Brian -- 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/
Re: xterm doesn't open on start (was: checkX problems)
Timares, Brian (Patriot) wrote: Lothar Brendel wrote: [...] Thus, once more: What does md5sum /usr/bin/checkX yield? a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216? The 2nd: vhaisbtim...@isb-timaresbrian-lt ~ $ md5sum /usr/bin/checkX a36409714f5ce9d01e8dfb4cb38b7216 */usr/bin/checkX ... and that's the checksum for the version 0.3.0 of checkX! $ checkX -v run2 0.3.0 Ok, yes, that's an easier version check :-) So, you've got the situation I surmised in http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html I.e. you *don't* have the new version (0.3.1) of the run2-package installed. Install that and retry, please. Ciao Lothar -- 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/
RE: xterm doesn't open on start (was: checkX problems)
Lothar Brendel wrote: Timares, Brian (Patriot) wrote: Lothar Brendel wrote: $ checkX -v run2 0.3.0 So, you've got the situation I surmised in http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html Grr, I saw that, went and _thought_ I got the right version but it seems the right version wasn't avaiable at the time and I got fooled by the 0.3.0-1 to think 0.3.1. I have carefully upgraded, and when running Setup17.exe I saw it wanted to revert, but I didn't let it. The X window showed up, but it blew up real good (the windows disappeared, then the X icon. After a rebootit didn't launch at all. I ran startxwin.sh from the Cygwin Bash Shell, and it started. After quitting that I launched it from startxwin.bat and the windows showed up but they died after a second at most and no X icon in the taskbar tray.. Same thing after reboot. This time I after launching from a Cygwin Bash Shell (successfully) I closed the cygwin bash shell and the X Window died. The X server kept running. Brian -- 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/
Re: xterm doesn't open on start (was: checkX problems)
Timares, Brian (Patriot) wrote: Lothar Brendel wrote: Timares, Brian (Patriot) wrote: Lothar Brendel wrote: $ checkX -v run2 0.3.0 So, you've got the situation I surmised in http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html Grr, I saw that, went and _thought_ I got the right version but it seems the right version wasn't avaiable at the time and I got fooled by the 0.3.0-1 to think 0.3.1. I have carefully upgraded, and when running Setup17.exe I saw it wanted to revert, but I didn't let it. Exactly, the evil setup tries to revert it to 0.3.0-1 every time. Quite easy to forget keeping an eye on that when tinkering with other packages. The X window showed up, but it blew up real good (the windows disappeared, then the X icon. After a rebootit didn't launch at all. I ran startxwin.sh from the Cygwin Bash Shell, and it started. At least we're getting *somewhere* :-) Ok, what happens when entering the two vital commands by hand in the the Cygwin Bash Shell (waiting with the second until the X-icon has appeared)? XWin -multiwin xterm -display :0 Reproducible success? Asks Lothar -- 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/
RE: xterm doesn't open on start (was: checkX problems)
Lothar Brendel wrote: Timares, Brian (Patriot) wrote: The X window showed up, but it blew up real good (the windows disappeared, then the X icon. After a rebootit didn't launch at all. I ran startxwin.sh from the Cygwin Bash Shell, and it started. At least we're getting *somewhere* :-) Ok, what happens when entering the two vital commands by hand in the the Cygwin Bash Shell (waiting with the second until the X-icon has appeared)? XWin -multiwin xterm -display :0 Reproducible success? I'll try again from home (I went into the office to simplify things). Here is what I got (sorry for the word-wrap): vhaisbtim...@isb-timaresbrian-lt ~ $ XWin -multiwindow [1] 5004 vhaisbtim...@isb-timaresbrian-lt ~ $ Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/isb-timaresbrian-lt:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winPrefsLoadPreferences: /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winGetDisplay: DISPLAY=:0.0 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 3200 height: 1200 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello Screen 0 added at XINERAMA coordinate (0,0). winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shar ed memory support in the kernel (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 winPointerWarpCursor - Discarding first warp: 1600 600 (--) 3 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 Rules = base Model = pc105 Layout = us Variant = none Options = none winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winGetDisplay: DISPLAY=:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=:0.0 winGetDisplay: DISPLAY=:0.0 winMultiWindowXMsgProc - DISPLAY=:0.0 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winGetDisplay: DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp lay. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di splay. winClipboardProc - XOpenDisplay () returned and successfully opened the display. From the xterm, which has stayed open: vhaisbtim...@isb-timaresbrian-lt ~ $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 5516 15516 55160 180490 16:51:58 /usr/bin/bash 3868 13868 3868? 180490 16:52:02 /usr/bin/ssh-agent 500455165004 46120 180490 16:54:07 /usr/bin/XWin 4064551640649240 180490 16:56:09 /usr/bin/xterm 601240646012 51441 180490 16:56:10 /usr/bin/bash 218460122184 42401 180490 16:56:21 /usr/bin/ps Brian Timares -- 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/
RE: xterm doesn't open on start (was: checkX problems)
Just to be clear from the start, Cygwin 1.7 not 1.5. And I tried to make this clear. And I tried to not let Outlook's word-wrap inter- fere. Lothar Brendel wrote: Timares, Brian (Patriot) wrote: Lothar Brendel wrote: Timares, Brian (Patriot) wrote: Lothar Brendel wrote: My guess: It's the old checkX-problem again because you're using version 0.3.0-1 of the run2-package. Do to some reason unknown to me, that's the default version. But we need 0.3.1-1, which you only get when Tried it, including changing XWin Server to C:\cygwin\bin\run2.exe /usr/bin/startxwin.bat That was a misunderstanding. I didn't mean to use ``run2'' instead of ``run'' but to verify that the version of the *package* 'run2' (containing ``checkX'') is the most recent one. Did you do that? You were clear. I did get the 0.3.1-1 and it showed up just as you said. IC, but could you please perform the following two tests nevertheless? First open Cygwin's standard bash console, then enter: Ran Cygwin Bash Shell, which has a Target of C:\cygwin\Cygwin.bat : Initialising new SSH agent... succeeded Enter passphrase for /home/VHAISBTIMARB/.ssh/id_rsa: Bad passphrase, try again for /home/VHAISBTIMARB/.ssh/id_rsa: Identity added: /home/VHAISBTIMARB/.ssh/id_rsa (/home/VHAISBTIMARB/.ssh/id_rsa) vhaisbtim...@isb-timaresbrian-lt ~ $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 4676 14676 46760 180490 09:16:53 /usr/bin/bash 4824 14824 4824? 180490 09:16:54 /usr/bin/ssh-agent 554846765548 16080 180490 09:17:30 /usr/bin/ps i) ```time checkX -t 12'' How long does it take? vhaisbtim...@isb-timaresbrian-lt ~ $ time checkX -t 12 real0m0.098s user0m0.046s sys 0m0.031s ii) ``startxwin.sh'' Any messages? Yes, see below, but after reviewing it all I tried it with various items on and off and having the One-VA VPN client (Cisco VPN Client 5) off makes the difference. It is odd, though, that if I run startxwin.sh again, it works the second time, even though the VPN is on. Also, if I quit X Windows (making sure the ssh-agent process is gone) and relaunch everything works fine. It is just the first time that I have trouble if the VPN is on. I believe the VPN hadn't caused me problems with Cygwin's X Windows implementation, but I can't say that with 100% certainty. Anyway, here is the key difference to no VPN versus VPN on: diff working.txt broken.txt 7a8 xterm Xt error: Can't open display: 127.0.0.1:0.0 ... Long version at the bottom. I note that 9.11. Cannot Open Display: 127.0.0.1:0.0 on the referenced page http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cannot-open-display apparently needs the text changed (added?) to: Can't open display: 127.0.0.1:0.0. 1) Why does launching it again work? Because it doesn't need me to enter my key's password? 2) Why does quitting/launching after it has worked once work? Again, is it because of it not needing my input? 3) If I go my preferred 'XWin Server' to launch it, it doesn't work, not even the X icon shows up. If I launch that again, it works. If I open a cygwin bash shell (before the 2nd launch) and check processes it shows: vhaisbtim...@isb-timaresbrian-lt ~ $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 3076 13076 30760 180490 14:01:32 /usr/bin/bash 600 1 600600? 180490 14:01:47 /usr/bin/ssh-agent I172430763076 33360 180490 14:01:47 /usr/bin/ssh-add 3304 13304 33041 180490 14:02:05 /usr/bin/bash 318833043188 25681 180490 14:02:09 /usr/bin/ps What I want is to have an alias to XWin Server (currently its Target is C:\cygwin\bin\run.exe /usr/bin/startxwin.bat) in my startup items so I always get X Windows, and always am prompted in an xterm for my ssh key's password. What I'll try next: Update to the current version of cygwin (hopefully the new termcap gets rid of the 'clear screen after viewing man page or running vi' issue AKA the -X option in less AKA the 'XTerm*titeInhibit: true' issue) and see if that helps, but it appears I just have to be careful to launch the VPN after starting X Windows after launching a cygwin bash shell. -- long (complete) version of startxwin.sh with VPN on: vhaisbtim...@isb-timaresbrian-lt ~ $ startxwin.sh Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow -clipboard -silent-dup-error vhaisbtim...@isb-timaresbrian-lt ~ $ xterm Xt error: Can't open display: 127.0.0.1:0.0 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/isb-timaresbrian-lt:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 winValidateArgs - g_iNumScreens: 1
RE: xterm doesn't open on start (was: checkX problems)
I wrote: And I tried to make this clear. email -^ *sigh* Sorry! Brian -- 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/
Re: xterm doesn't open on start (was: checkX problems)
Timares, Brian (Patriot) wrote: Just to be clear from the start, Cygwin 1.7 not 1.5. ACK. [...] i) ```time checkX -t 12'' How long does it take? vhaisbtim...@isb-timaresbrian-lt ~ $ time checkX -t 12 real0m0.098s user0m0.046s sys 0m0.031s And *that* shouldn't happen! I don't quite get your VPN setup, but it being active *may* cause a delay in getting up the X server, and that *may* cause xterm to loose its patience. ii) ``startxwin.sh'' Any messages? Yes, see below, but after reviewing it all I tried it with various items on and off and having the One-VA VPN client (Cisco VPN Client 5) off makes the difference. It is odd, though, that if I run startxwin.sh again, it works the second time, even though the VPN is on. Not really, I think. The message xterm Xt error: Can't open display: 127.0.0.1:0.0 indicates that xterm didn't find the X server being up. And the reason is ``checkX'' not doing its job, namely waiting until it is really up. If you then start ``startxwin.sh'' again, it complains about an X server already being up, but at least xterm can finally connect. Thus, once more: What does md5sum /usr/bin/checkX yield? a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216? Asks Lothar -- 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/
Re: xterm doesn't open on start (was: checkX problems)
Timares, Brian (Patriot) wrote: Lothar Brendel wrote: Timares, Brian (Patriot) wrote: Lothar Brendel wrote: My guess: It's the old checkX-problem again because you're using version 0.3.0-1 of the run2-package. Do to some reason unknown to me, that's the default version. But we need 0.3.1-1, which you only get when Tried it, including changing XWin Server to C:\cygwin\bin\run2.exe /usr/bin/startxwin.bat That was a misunderstanding. I didn't mean to use ``run2'' instead of ``run'' but to verify that the version of the *package* 'run2' (containing ``checkX'') is the most recent one. Did you do that? You were clear. I did get the 0.3.1-1 and it showed up just as you said. IC, but could you please perform the following two tests nevertheless? First open Cygwin's standard bash console, then enter: i) ```time checkX -t 12'' How long does it take? ii) ``startxwin.sh'' Any messages? Ciao Lothar -- 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/
Re: xterm doesn't open on start (was: checkX problems)
Timares, Brian (Patriot) wrote: [...] Nothing works. 1.7 doesn't work for me out-of-the-box (yes, I ripped it all out and tried it fresh :-) I open a DOS box and check processes and see bash running with an l or a 1 in the left columnn, but nothing appears. If I launch an Xterm it opens up. It seems some of the login thing happen, but when I add in my ssh-agent starting script, since it requires input, it fails (http://mah.everybody.org/docs/ssh is the script I use). Any other ideas? Doen't look like the issue http://cygwin.com/ml/cygwin-xfree/2009-11/msg00174.html to me. My guess: It's the old checkX-problem again because you're using version 0.3.0-1 of the run2-package. Do to some reason unknown to me, that's the default version. But we need 0.3.1-1, which you only get when explicitely (triple-)clicking its circular double-arrow (how's that thingy called BTW?) in the Utils category. Maybe Chuck can tell why we don't get the new version as default. Ciao Lothar -- 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/
Re: xterm doesn't open on start (was: checkX problems)
Timares, Brian (Patriot) wrote: Lothar Brendel wrote: [...] My guess: It's the old checkX-problem again because you're using version 0.3.0-1 of the run2-package. Do to some reason unknown to me, that's the default version. But we need 0.3.1-1, which you only get when explicitely (triple-)clicking its circular double-arrow (how's that thingy called BTW?) in the Utils category. Tried it, including changing XWin Server to C:\cygwin\bin\run2.exe /usr/bin/startxwin.bat That was a misunderstanding. I didn't mean to use ``run2'' instead of ``run'' but to verify that the version of the *package* 'run2' (containing ``checkX'') is the most recent one. Did you do that? Asks Lothar -- 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/
RE: xterm doesn't open on start (was: checkX problems)
Lothar Brendel wrote: Timares, Brian (Patriot) wrote: Lothar Brendel wrote: My guess: It's the old checkX-problem again because you're using version 0.3.0-1 of the run2-package. Do to some reason unknown to me, that's the default version. But we need 0.3.1-1, which you only get when Tried it, including changing XWin Server to C:\cygwin\bin\run2.exe /usr/bin/startxwin.bat That was a misunderstanding. I didn't mean to use ``run2'' instead of ``run'' but to verify that the version of the *package* 'run2' (containing ``checkX'') is the most recent one. Did you do that? You were clear. I did get the 0.3.1-1 and it showed up just as you said. It didn't help, so then I tried changing run to run2, but changed it all back since it didn't help. Brian by the way, Outlook makes proper quoting a royal pain :-/ -- 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/
