xterm no longer accepts keyboard input

[Bob Kline]

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:bkline@rksystems.com

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: XWin.0.log
URL: <http://cygwin.com/pipermail/cygwin-xfree/attachments/20100314/7beafc4f/attachment.log>
-------------- next part --------------
--
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/