|

»

Problems with Cygwin/X xterm -- not responding to keyboard

View: New views

6 Messages — Rating Filter: Alert me

	Problems with Cygwin/X xterm -- not responding to keyboard by Back, Michael :: Rate this Message: \| View Threaded \| Show Only this Message Hi, I'm having a problem since I updated Cygwin early last week. When I start X via startxwin.bat (which %RUN%'s an xterm), or run xterm from right-click on the tray icon, or create a new xterm from Cygwin Prompt (cygwin.bat), none of these xterms will respond to keyboard. I can start rxvt from the Cygwin prompt (cygwin.bat) & get that to respond to keyboard, but not if I include the %RUN% rxvt in startxwin.bat. This is my "/tmp/XWin.log": $ cat XWin.log _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winPrefsLoadPreferences: /usr/lib/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 3200 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 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 winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 (--) 3 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) (--) Using preset keyboard for "English (USA)" (409), type "4" Could not init font path element /usr/share/fonts/TTF/, removing from list! Could not init font path element /usr/share/fonts/OTF, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitClipboard () winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winProcEstablishConnection - winInitClipboard returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp lay. winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcSetSelectionOwner - Clipboard not yet started, aborting. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di splay. winProcSetSelectionOwner - Clipboard not yet started, aborting. winDeinitMultiWindowWM - Noting shutdown in progress winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winDeinitMultiWindowWM - Noting shutdown in progress mback@mback /tmp $ Also, I now have menus in the xterm whereas before the update, I had no menus. The XTerm seems also to be ignoring my .Xdefaults file. Can you help me understand what's going on? Thanks, Michael -- 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: Problems with Cygwin/X xterm -- not responding to keyboard by Back, Michael :: Rate this Message: \| View Threaded \| Show Only this Message Michael Back wrote: > I'm having a problem since I updated Cygwin early last week. When I start X > via startxwin.bat (which %RUN%'s an xterm), or run xterm from right-click on [snip] I figured it out. When I located the recently moved startxwin.bat script in /bin, and started it from that location, XTerm magically started receiving my keystrokes. Wish it were not so sensitive to the startup directory... Shortcut to startxwin properties: Target: C:\cygwin\bin\startxwin.bat Start in: C:\cygwin\bin > The XTerm seems also to be ignoring my .Xdefaults file. I'm still having problems with Xdefaults -- can't yet get XTerm to respond to the following: XTerm.VT100.font: --bitstream vera sans mono-medium--r--16------- XTerm.VT100.boldFont: --bitstrean vera sans mono-bold--r--16------- XTerm.VT100.background: Black XTerm.VT100.foreground: Gray XTerm.cursorColor: Green The terminal remains black characters on a white background. Thanks, Michael -- 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: Problems with Cygwin/X xterm -- not responding to keyboard by Yaakov (Cygwin/X) :: Rate this Message: \| View Threaded \| Show Only this Message -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Back, Michael wrote: > I'm still having problems with Xdefaults -- can't yet get XTerm to respond to the following: > > XTerm.VT100.font: --bitstream vera sans mono-medium--r--16------- > XTerm.VT100.boldFont: --bitstrean vera sans mono-bold--r--16------- > XTerm.VT100.background: Black > XTerm.VT100.foreground: Gray > XTerm.cursorColor: Green Have you tried "xrdb -load ~/.Xdefaults"? (xrdb is in its own package.) Yaakov Cygwin/X -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkiMV4ACgkQpiWmPGlmQSO29QCg3o5EioAeGwyehNu75wBrwScU uH0Ani603o6r3/mMakYORrIlQHoBYuLQ =riJ8 -----END PGP SIGNATURE----- -- 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: Problems with Cygwin/X xterm -- not responding to keyboard by Back, Michael :: Rate this Message: \| View Threaded \| Show Only this Message Yaakov, Thanks for your help... Yaakov wrote: >Back, Michael wrote: >> I'm still having problems with Xdefaults -- can't yet get >XTerm to respond to the following: >> >> XTerm.VT100.font: --bitstream vera sans mono-medium--r--16------- >> XTerm.VT100.boldFont: --bitstrean vera sans mono-bold--r--16------- >> XTerm.VT100.background: Black >> XTerm.VT100.foreground: Gray >> XTerm.cursorColor: Green > >Have you tried "xrdb -load ~/.Xdefaults"? (xrdb is in its own >package.) mback@mback ~ $ xrdb -load ~/.Xdefaults cpp: too many input files mback@mback ~ $ Thanks, Michael -- 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: Problems with Cygwin/X xterm -- not responding to keyboard by mohnkern :: Rate this Message: \| View Threaded \| Show Only this Message Back, Michael wrote: Hi, I'm having a problem since I updated Cygwin early last week. When I start X via startxwin.bat (which %RUN%'s an xterm), or run xterm from right-click on the tray icon, or create a new xterm from Cygwin Prompt (cygwin.bat), none of these xterms will respond to keyboard. I can start rxvt from the Cygwin prompt (cygwin.bat) & get that to respond to keyboard, but not if I include the %RUN% rxvt in startxwin.bat. This is my "/tmp/XWin.log": $ cat XWin.log _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winPrefsLoadPreferences: /usr/lib/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 3200 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 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 winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 (--) 3 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) (--) Using preset keyboard for "English (USA)" (409), type "4" Could not init font path element /usr/share/fonts/TTF/, removing from list! Could not init font path element /usr/share/fonts/OTF, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitClipboard () winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winProcEstablishConnection - winInitClipboard returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp lay. winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcSetSelectionOwner - Clipboard not yet started, aborting. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di splay. winProcSetSelectionOwner - Clipboard not yet started, aborting. winDeinitMultiWindowWM - Noting shutdown in progress winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winDeinitMultiWindowWM - Noting shutdown in progress mback@mback /tmp $ Also, I now have menus in the xterm whereas before the update, I had no menus. The XTerm seems also to be ignoring my .Xdefaults file. Can you help me understand what's going on? Thanks, Michael -- 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/ I'm encountering the same problem, the Xterm Window comes up fine, but I can't get any response from the keyboard.
	Re: Problems with Cygwin/X xterm -- not responding to keyboard by Jon TURNEY :: Rate this Message: \| View Threaded \| Show Only this Message mohnkern wrote: > > > Back, Michael wrote: >> Hi, >> >> I'm having a problem since I updated Cygwin early last week. When I start >> X via startxwin.bat (which %RUN%'s an xterm), or run xterm from >> right-click on the tray icon, or create a new xterm from Cygwin Prompt >> (cygwin.bat), none of these xterms will respond to keyboard. I can start >> rxvt from the Cygwin prompt (cygwin.bat) & get that to respond to >> keyboard, but not if I include the %RUN% rxvt in startxwin.bat. >> > > I'm encountering the same problem, the Xterm Window comes up fine, but I > can't get any response from the keyboard. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-i-cant-type-anything -- 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/