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/