Re: xterm no longer accepts keyboard input
Larry Hall (Cygwin X reply-to-list-only-lh-x at cygwin.com writes: On 5/6/2010 3:18 AM, Jyh-Shyong Ho wrote: I read a series of discussion on this problem, have you been able to solve this problem? http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-i-cant-type-anything Hi, Larry, I have tried use FAQ's step to unset XkeysysDB on my cygwin, but still not work. also I have using command 'source /etc/profile.d/xinit.sh' to unset XkeysysDB. But, still not work. How could I make sure the XkeysysDB unset properly? Anyone could give me a hand would appreciate. Regards josh -- 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 no longer accepts keyboard input
Hi, I read a series of discussion on this problem, have you been able to solve this problem? I just had a PC with 64-bit Windows 7 installed, and try to install CYGWIN/X on it, I encountered the same problem: the xterm no longer accepts keyboard input. I tried various methods to solve this problem but failed, so I like to know how do you make the CYGWIN/X work again? I have been using the old version of CYGWIN/X on WindowsXP and Windows VISTA for a long time without any problem. Thank you. -- 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 no longer accepts keyboard input
On 5/6/2010 3:18 AM, Jyh-Shyong Ho wrote: I read a series of discussion on this problem, have you been able to solve this problem? http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-i-cant-type-anything -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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 no longer accepts keyboard input
On 13/03/2010 21:47, Bob Kline wrote: On 3/13/2010 1:05 PM, Bob Kline wrote: I have used X under Cygwin successfully for years. Yesterday I did an upgrade of my Cygwin installation and X stopped working. After struggling to get things working again, I decided to just install Cygwin fresh and start over. Now I can get the X server started (following the instructions in the Cygwin/X User's Guide, running /usr/bin/startxwin from a Cygwin shell), but xterm windows that I open do not respond to keyboard input. I looked at the FAQ and found the entry (3.2 I upgraded my X server and now I can't type anything into any X application) which warns against using any older scripts to launch X, but as noted above, I'm invoking the startxwin binary directly. Any thoughts as to what could be going wrong, given that this is an installation of Cygwin and X from scratch? looking at your cygcheck.out, you have the following variables in your environment XKEYSYMDB = '/usr/X11R6/lib/X11/XKeysymDB' XAPPLRESDIR = '/usr/X11R6/lib/X11/app-defaults' XCMSDB = '/usr/X11R6/lib/X11/Xcms.txt' XNLSPATH = '/usr/X11R6/lib/X11/locale' These have probably been set by Microsoft Services for Unix, and as the FAQ tries to make clear, at least XKEYSYMDB must be unset for keyboard input to XWin to work correctly (FAQ 3.2 refers to FAQ 8.8) We used to have something in startxwin.bat to unset this, so I guess it is a regression that we don't do that anymore. Following up on my earlier post, I see that although I am able to start the X server if I invoke /usr/bin/startxwin directly from a Cygwin shell, that's not *exactly* what the FAQ was suggesting. I'm not sure if the difficulties starting a server mean you have some other problem as well. -- 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/
Re: xterm no longer accepts keyboard input
On 15/03/2010 05:42, David Barr wrote: On Sun, Mar 14, 2010 at 7:17 AM, Jeff Spirkospi...@gmail.com wrote: The icon runs from the Windows environment, so the run.exe and bash.exe wrapper programs are needed to set up the proper cygwin environment. Once you're in a cygwin shell, you already have the cygwin environment set up. That's why you don't need to type them in from the command line. So, they really should be equivalent. I've probably missed a prior discussion, but if startxwin.exe doesn't set up the Cygwin environment, then what good is it? I thought that this was about the only advantage that startxwin.bat had over startx. No. startx and startxwin are different tools to solve different problems. I keep adding more text to [1] to clarify this, but this doesn't appear to help, perhaps because nobody actually reads it... [1] http://x.cygwin.com/docs/ug/using.html#using-starting Considering that startx also sets up the .Xauthority file and startxwin.exe doesn't, I see absolutely no reason to use startxwin.exe instead of startx. -- 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/
Re: xterm no longer accepts keyboard input
On 3/15/2010 1:35 PM, Jon TURNEY wrote: ... I'm not sure if the difficulties starting a server mean you have some other problem as well. Thanks for your response, Jon. As you'll see from a more recent post, I was able to solve both problems by going back to using a script instead of the compiled binary for startxwin. -- Bob Kline http://www.rksystems.com mailto:bkl...@rksystems.com -- 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 no longer accepts keyboard input
On Mon, Mar 15, 2010 at 10:44 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: No. startx and startxwin are different tools to solve different problems. I keep adding more text to [1] to clarify this, but this doesn't appear to help, perhaps because nobody actually reads it... [1] http://x.cygwin.com/docs/ug/using.html#using-starting I read it. I just don't agree with it. These appear to be the reasons: 1) startxwin supplies the -multiwindow option to XWin.exe So does startx if you put that in the shortcut. 2) It uses a different script to start clients (~/.startxwinrc rather than ~/.xinitrc), because ~/.xinitrc will normally end by starting a window manager, which would be incorrect for ~/.startxwinrc (as it would discover the internal window manager is already running and exit immediately). In my opinion, it doesn't really matter with .xinitrc normally ends with. We can end it with anything that we want. It sounds like you can get the startxwin behavior (if that's what you really want) from startx if you put sh ~/.startxwinrc while : ; do sleep 1000; done in your .xinitrc. 3) startxwin exits after ~/.startxwinrc has completed and leaves XWin.exe running, whereas startx waits until ~/.xinitrc exits (which is usually waiting for the window manager started by it to exit) and then kills XWin.exe. If you don't like the behavior of startx exiting after the .xinitrc is complete, then why not write your .xinitrc so that it doesn't exit? Is it really worth maintaining another program when you can get the same behavior out of existing programs through config changes? Additionally, the startxwin.exe program is missing the security feature of creating a .Xauthority file. -- 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 no longer accepts keyboard input
On Sat, Mar 13, 2010 at 11:39 PM, Bob Kline bkl...@rksystems.com wrote: Jeff Spirko wrote: If you see different results from running startxwin from the command line vs. the icon, you should check to see if you have an old batch file laying around Thanks for the suggestion. I looked again for any old scripts which might be found by the shell, but there aren't any. The difference in behavior may be accounted for by the fact that the shortcut doesn't actually have the same command line as is recommended by the users' guide, which advises running simply /usr/bin/startxwin from a Cygwin shell. The command line used by the shortcut is instead: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe The icon runs from the Windows environment, so the run.exe and bash.exe wrapper programs are needed to set up the proper cygwin environment. Once you're in a cygwin shell, you already have the cygwin environment set up. That's why you don't need to type them in from the command line. So, they really should be equivalent. -- Jeff Spirko spi...@gmail.com spi...@lehigh.edu WD3V |= The study of non-linear physics is like the study of non-elephant biology. -- 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 no longer accepts keyboard input
On 3/14/2010 10:17 AM, Jeff Spirko wrote: The icon runs from the Windows environment, so the run.exe and bash.exe wrapper programs are needed to set up the proper cygwin environment. Once you're in a cygwin shell, you already have the cygwin environment set up. That's why you don't need to type them in from the command line. So, they really should be equivalent. I would have thought so, too. However, the fact remains that the outcomes are different for the two methods of starting X. I can live with working around the second problem (that launching X using the shortcut doesn't work at all) by invoking startxwin.exe directly. I'm much more eager to solve the original problem (X no longer recognizes input from the keyboard). So, while I don't want to discourage anyone from looking for clues to solving the keyboard input problem in the log file from the launch of X which blows up, I am focusing on the original problem myself. Attached is the log file from launch of X which does *not* result in the failure dialog window, but whose X session is not able to use input from the keyboard. -- Bob Kline http://www.rksystems.com mailto:bkl...@rksystems.com Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.5.0 (10705000) Build Date: 2010-02-25 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1920 h 1200 winInitializeDefaultScreens - Returning 2010-03-14 12:12:19 (WW) /tmp mounted in textmode 2010-03-14 12:12:19 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 2010-03-14 12:12:19 _XSERVTransOpen: transport open failed for inet6/xp:0 2010-03-14 12:12:19 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 2010-03-14 12:12:20 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2010-03-14 12:12:20 (II) xorg.conf is not supported 2010-03-14 12:12:20 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2010-03-14 12:12:20 LoadPreferences: /cygdrive/c/home/bkline/.XWinrc not found 2010-03-14 12:12:20 LoadPreferences: Loading /etc/X11/system.XWinrc 2010-03-14 12:12:20 LoadPreferences: Done parsing the configuration file... 2010-03-14 12:12:20 winGetDisplay: DISPLAY=:0.0 2010-03-14 12:12:20 winDetectSupportedEngines - Windows NT/2000/XP 2010-03-14 12:12:20 winDetectSupportedEngines - DirectDraw installed 2010-03-14 12:12:20 winDetectSupportedEngines - DirectDraw4 installed 2010-03-14 12:12:20 winDetectSupportedEngines - Returning, supported engines 0007 2010-03-14 12:12:20 winSetEngine - Multi Window or Rootless = ShadowGDI 2010-03-14 12:12:20 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2010-03-14 12:12:20 winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1200 depth: 32 2010-03-14 12:12:20 winFinishScreenInitFB - Masks: 00ff ff00 00ff 2010-03-14 12:12:20 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 2010-03-14 12:12:20 null screen fn ReparentWindow 2010-03-14 12:12:20 null screen fn RestackWindow 2010-03-14 12:12:20 InitQueue - Calling pthread_mutex_init 2010-03-14 12:12:20 InitQueue - pthread_mutex_init returned 2010-03-14 12:12:20 InitQueue - Calling pthread_cond_init 2010-03-14 12:12:20 InitQueue - pthread_cond_init returned 2010-03-14 12:12:20 winInitMultiWindowWM - Hello 2010-03-14 12:12:20 winMultiWindowXMsgProc - Hello 2010-03-14 12:12:20 Screen 0 added at XINERAMA coordinate (0,0). 2010-03-14 12:12:20 winInitMultiWindowWM - Calling pthread_mutex_lock () 2010-03-14 12:12:20 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2010-03-14 12:12:20 MIT-SHM extension disabled due to lack of kernel support 2010-03-14 12:12:20 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2010-03-14 12:12:20 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2010-03-14 12:12:20 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2010-03-14 12:12:28 winPointerWarpCursor - Discarding first warp: 960 600 2010-03-14 12:12:28 (--) 3 mouse buttons found 2010-03-14 12:12:28 (--) Setting autorepeat to delay=500, rate=31 2010-03-14 12:12:28 (--) winConfigKeyboard - Layout: 0409 (0409) 2010-03-14 12:12:28 (--) Using preset keyboard for English (USA) (409), type 4 2010-03-14 12:12:28 Rules = base Model = pc105 Layout = us Variant = none Options = none 2010-03-14 12:12:28 winInitMultiWindowWM - pthread_mutex_lock () returned. 2010-03-14 12:12:28 winProcEstablishConnection - Hello 2010-03-14 12:12:28 winInitClipboard () 2010-03-14 12:12:28 winInitMultiWindowWM - pthread_mutex_unlock () returned. 2010-03-14 12:12:28 winMultiWindowXMsgProc - pthread_mutex_lock () returned. 2010-03-14 12:12:28 winGetDisplay: DISPLAY=:0.0 2010-03-14 12:12:28 winProcEstablishConnection - winInitClipboard returned. 2010-03-14
Re: xterm no longer accepts keyboard input
On 3/14/2010 12:20 PM, Bob Kline wrote: Attached is the log file from launch of X which does *not* result in the failure dialog window, but whose X session is not able to use input from the keyboard. Sorry, that was the wrong log file (from an attempt to launch X from the shortcut). Here is the log file from an X session created by invoking startxwin.exe directly from a bash console window. -- Bob Kline http://www.rksystems.com mailto:bkl...@rksystems.com Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.5.0 (10705000) Build Date: 2010-02-25 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1920 h 1200 winInitializeDefaultScreens - Returning 2010-03-14 12:22:18 (WW) /tmp mounted in textmode 2010-03-14 12:22:18 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 2010-03-14 12:22:18 _XSERVTransOpen: transport open failed for inet6/xp:0 2010-03-14 12:22:18 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 2010-03-14 12:22:19 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2010-03-14 12:22:19 (II) xorg.conf is not supported 2010-03-14 12:22:19 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2010-03-14 12:22:19 LoadPreferences: /cygdrive/c/home/bkline/.XWinrc not found 2010-03-14 12:22:19 LoadPreferences: Loading /etc/X11/system.XWinrc 2010-03-14 12:22:19 LoadPreferences: Done parsing the configuration file... 2010-03-14 12:22:19 winGetDisplay: DISPLAY=:0.0 2010-03-14 12:22:19 winDetectSupportedEngines - Windows NT/2000/XP 2010-03-14 12:22:19 winDetectSupportedEngines - DirectDraw installed 2010-03-14 12:22:19 winDetectSupportedEngines - DirectDraw4 installed 2010-03-14 12:22:19 winDetectSupportedEngines - Returning, supported engines 0007 2010-03-14 12:22:19 winSetEngine - Multi Window or Rootless = ShadowGDI 2010-03-14 12:22:19 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2010-03-14 12:22:19 winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1200 depth: 32 2010-03-14 12:22:19 winFinishScreenInitFB - Masks: 00ff ff00 00ff 2010-03-14 12:22:19 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 2010-03-14 12:22:19 null screen fn ReparentWindow 2010-03-14 12:22:19 null screen fn RestackWindow 2010-03-14 12:22:19 InitQueue - Calling pthread_mutex_init 2010-03-14 12:22:19 InitQueue - pthread_mutex_init returned 2010-03-14 12:22:19 InitQueue - Calling pthread_cond_init 2010-03-14 12:22:19 InitQueue - pthread_cond_init returned 2010-03-14 12:22:19 winInitMultiWindowWM - Hello 2010-03-14 12:22:19 winMultiWindowXMsgProc - Hello 2010-03-14 12:22:19 Screen 0 added at XINERAMA coordinate (0,0). 2010-03-14 12:22:19 winInitMultiWindowWM - Calling pthread_mutex_lock () 2010-03-14 12:22:19 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2010-03-14 12:22:19 MIT-SHM extension disabled due to lack of kernel support 2010-03-14 12:22:19 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2010-03-14 12:22:19 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2010-03-14 12:22:19 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2010-03-14 12:22:29 winPointerWarpCursor - Discarding first warp: 960 600 2010-03-14 12:22:29 (--) 3 mouse buttons found 2010-03-14 12:22:30 (--) Setting autorepeat to delay=500, rate=31 2010-03-14 12:22:30 (--) winConfigKeyboard - Layout: 0409 (0409) 2010-03-14 12:22:30 (--) Using preset keyboard for English (USA) (409), type 4 2010-03-14 12:22:30 Rules = base Model = pc105 Layout = us Variant = none Options = none 2010-03-14 12:22:30 winInitMultiWindowWM - pthread_mutex_lock () returned. 2010-03-14 12:22:30 winProcEstablishConnection - Hello 2010-03-14 12:22:30 winInitMultiWindowWM - pthread_mutex_unlock () returned. 2010-03-14 12:22:30 winMultiWindowXMsgProc - pthread_mutex_lock () returned. 2010-03-14 12:22:30 winInitClipboard () 2010-03-14 12:22:30 winGetDisplay: DISPLAY=:0.0 2010-03-14 12:22:30 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. 2010-03-14 12:22:30 winInitMultiWindowWM - DISPLAY=:0.0 2010-03-14 12:22:30 winGetDisplay: DISPLAY=:0.0 2010-03-14 12:22:30 winClipboardProc - Hello 2010-03-14 12:22:30 winProcEstablishConnection - winInitClipboard returned. 2010-03-14 12:22:30 winMultiWindowXMsgProc - DISPLAY=:0.0 2010-03-14 12:22:30 DetectUnicodeSupport - Windows NT/2000/XP 2010-03-14 12:22:30 winGetDisplay: DISPLAY=:0.0 2010-03-14 12:22:30 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. 2010-03-14 12:22:30 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. 2010-03-14 12:22:30 winClipboardProc - DISPLAY=:0.0 2010-03-14 12:22:30 winClipboardProc - XOpenDisplay () returned and
Re: xterm no longer accepts keyboard input
On Sun, Mar 14, 2010 at 7:17 AM, Jeff Spirko spi...@gmail.com wrote: The icon runs from the Windows environment, so the run.exe and bash.exe wrapper programs are needed to set up the proper cygwin environment. Once you're in a cygwin shell, you already have the cygwin environment set up. That's why you don't need to type them in from the command line. So, they really should be equivalent. I've probably missed a prior discussion, but if startxwin.exe doesn't set up the Cygwin environment, then what good is it? I thought that this was about the only advantage that startxwin.bat had over startx. Considering that startx also sets up the .Xauthority file and startxwin.exe doesn't, I see absolutely no reason to use startxwin.exe instead of startx. -- 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/
xterm no longer accepts keyboard input
I have used X under Cygwin successfully for years. Yesterday I did an upgrade of my Cygwin installation and X stopped working. After struggling to get things working again, I decided to just install Cygwin fresh and start over. Now I can get the X server started (following the instructions in the Cygwin/X User's Guide, running /usr/bin/startxwin from a Cygwin shell), but xterm windows that I open do not respond to keyboard input. I looked at the FAQ and found the entry (3.2 I upgraded my X server and now I can't type anything into any X application) which warns against using any older scripts to launch X, but as noted above, I'm invoking the startxwin binary directly. Any thoughts as to what could be going wrong, given that this is an installation of Cygwin and X from scratch? -- Bob Kline http://www.rksystems.com mailto:bkl...@rksystems.com -- 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 no longer accepts keyboard input
On Sat, Mar 13, 2010 at 4:47 PM, Bob Kline bkl...@rksystems.com wrote: On 3/13/2010 1:05 PM, Bob Kline wrote: I have used X under Cygwin successfully for years. Yesterday I did an upgrade of my Cygwin installation and X stopped working. After struggling to get things working again, I decided to just install Cygwin fresh and start over. Now I can get the X server started (following the instructions in the Cygwin/X User's Guide, running /usr/bin/startxwin from a Cygwin shell), but xterm windows that I open do not respond to keyboard input. I looked at the FAQ and found the entry (3.2 I upgraded my X server and now I can't type anything into any X application) which warns against using any older scripts to launch X, but as noted above, I'm invoking the startxwin binary directly. Any thoughts as to what could be going wrong, given that this is an installation of Cygwin and X from scratch? Following up on my earlier post, I see that although I am able to start the X server if I invoke /usr/bin/startxwin directly from a Cygwin shell, that's not *exactly* what the FAQ was suggesting. What the FAQ document actually suggests is that I start the X server by using the shortcut under Cygwin-X on the start menu. If you see different results from running startxwin from the command line vs. the icon, you should check to see if you have an old batch file laying around using commands like these: vdir /usr/bin/startxwin* which startxwin Unfortunately, I can't help with your actual problem, but this may be complicating things. -Jeff -- Jeff Spirko spi...@gmail.com spi...@lehigh.edu WD3V |= The study of non-linear physics is like the study of non-elephant biology. -- 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 no longer accepts keyboard input
Jeff Spirko wrote: If you see different results from running startxwin from the command line vs. the icon, you should check to see if you have an old batch file laying around Thanks for the suggestion. I looked again for any old scripts which might be found by the shell, but there aren't any. The difference in behavior may be accounted for by the fact that the shortcut doesn't actually have the same command line as is recommended by the users' guide, which advises running simply /usr/bin/startxwin from a Cygwin shell. The command line used by the shortcut is instead: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- Bob Kline http://www.rksystems.com mailto:bkl...@rksystems.com -- 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/
