x keyboard with most keys dead since update -- faq answer 3.2 no help
Hi Everyone Please help, I am quite desperate. The day before yesterday I inadvertently upgraded to the new version of X. I had had a slight problem -- emacs suddenly froze, and on restart, I found myself with a US keyboard layout throughout X. (I need latin-american). I thought that perhaps downloading setxkbmap using cygwin setup might help restore the keyboard layout, but I accidentally ended up downloading the whole current version of cygwin. On restarting the XWin server, I found that xterm now did not respond to the keyboard. More exactly, a little trial and error has shown that some keys work and some don't. The keys that do not work are the main alphanumeric and punctuation keys. But the spacebar, tab, enter, backspace, delete, cursor movement keys, all numberpad keys, the special / key, (and probably all the function keys also) all do work. I can also paste onto the command line. I have a Toshiba Satellite laptop running Windows Vista. I have been searching for an answer for the past two days. There is what seems to be the perfect solution in the Cygwin XFree FAQ -- question 3.2. Unfortunately I am already using the startxwin.bat from the /usr/bin directory. I have the same problem even when I start XWin by double-clicking on this exact file. Viewing the file shows no reference to the XKEYSYMDB environment variable, and when I paste echo $XKEYSYMDB into the xterm command line and press Enter, nothing but a blank line is produced. This seems to indicate that my problem is not the same as the problem that Answer 3.2 is the solution to. In my attempts to solve the problem I have done a complete reinstall-from-scratch of cygwin. Same result -- can't use the keyboard. I need cygwin for my work -- and I haven't been able to do any work for the last three days. Please help! Thanks Andrew Thomas Blake -- 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/
x keyboard with most keys dead since update -- more info: xev for two keys
Hi Here is xev output for a q key followed by a space. KeyPress event, serial 27, synthetic NO, window 0xa1, root 0x7c, subw 0x0, time 10376624, (1,81), root:(1862,343), state 0x10, keycode 24 (keysym 0x1000ebb, U0EBB), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 27, synthetic NO, window 0xa1, root 0x7c, subw 0x0, time 10376718, (1,81), root:(1862,343), state 0x10, keycode 24 (keysym 0x1000ebb, U0EBB), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 27, synthetic NO, window 0xa1, root 0x7c, subw 0x0, time 10379526, (1,81), root:(1862,343), state 0x10, keycode 65 (keysym 0x20, space), same_screen YES, XLookupString gives 1 bytes: (20) XmbLookupString gives 1 bytes: (20) XFilterEvent returns: False KeyRelease event, serial 27, synthetic NO, window 0xa1, root 0x7c, subw 0x0, time 10379666, (1,81), root:(1862,343), state 0x10, keycode 65 (keysym 0x20, space), same_screen YES, XLookupString gives 1 bytes: (20) XFilterEvent returns: False I hope this gives a clue. (The keysym entry seems wrong for the q key.) Thanks for any help. Andrew Thomas Blake -- 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: x keyboard with most keys dead since update -- faq answer 3.2 no help
Hi I forgot about your third suggestion -- and in fact setxkbmap us restores the keyboard! But leaves me with a US layout... So maybe the trouble is a corrupted la layout? Thanks for the help. Andrew Thomas Blake On Thu, Feb 19, 2009 at 5:26 PM, Blake Thomas Andrew blakethomasand...@gmail.com wrote: Here is the XWin log output, and cygcheck.out is attached. Thanks for your help. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.5.3.0 (20090205) Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/bin/XWin -multiwindow -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 800 winInitializeDefaultScreens - Returning (II) XF86Config 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... winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 2560 height: 1024 depth: 32 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 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 (--) 5 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 080A (080a) (--) Using preset keyboard for Latin American (80a), type 4 winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitClipboard () winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - DISPLAY=127.0.0.1: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. On Thu, Feb 19, 2009 at 4:48 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: Blake Thomas Andrew wrote: Hi Everyone Please help, I am quite desperate. The day before yesterday I inadvertently upgraded to the new version of X. I had had a slight problem -- emacs suddenly froze, and on restart, I found myself with a US keyboard layout throughout X. (I need latin-american). I thought that perhaps downloading setxkbmap using cygwin setup might help restore the keyboard layout, but I accidentally ended up downloading the whole current version of cygwin. On restarting the XWin server, I found that xterm now did not respond to the keyboard. May we see your /var/log/XWin.0.log, please. Does setting a different keyboard map using setxkbmap make any difference (as http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xkb-not-working)? Cygcheck output as asked for in http://cygwin.com/problems.html ? More exactly, a little trial and error has shown that some keys work and some don't. The keys that do not work are the main alphanumeric and punctuation keys. But the spacebar, tab, enter, backspace, delete, cursor movement keys, all numberpad keys, the special / key, (and probably all the function keys also) all do work. I can also paste onto the command line. I have a Toshiba Satellite laptop running Windows Vista. I have been searching for an answer for the past two days. There is what seems to be the perfect solution in the Cygwin XFree FAQ -- question 3.2. Unfortunately I am already using the startxwin.bat from the /usr/bin directory. I have the same problem even when I start XWin by double-clicking on this exact file. Viewing the file shows no reference to the XKEYSYMDB environment variable, and when I paste echo $XKEYSYMDB into the xterm command line and press Enter, nothing but a blank line is produced. This seems to indicate that my problem is not the same as the problem that Answer 3.2 is the solution to. In my attempts to solve the problem I have done a complete reinstall-from-scratch of cygwin. Same result -- can't use the keyboard. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem
AltGr works with only one key
Hi
I can't do |@\{}[] in X (they all need the AltGr key), but I can do #
perfectly, with the AltGr key. (It's the 3 key with AltGr)
I have a Toshiba laptop running Vista. I used to have a Toshiba with
XP and Cygwin X and never had this problem.
The non-X bash terminal window works fine.
Here's a sequence from xev where I press down the AltGr key, then
press and release the 1 key, then press and release the 2 key, then
press and release the 3 key and then release the AltGr key:
KeyPress event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4562077, (71,548), root:(146,643),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4562077, (71,548), root:(146,643),
state 0x4, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4564542, (71,548), root:(146,643),
state 0x84, keycode 10 (keysym 0x7c, bar), same_screen YES,
XLookupString gives 1 bytes: (1c)
XmbLookupString gives 1 bytes: (1c)
XFilterEvent returns: False
KeyRelease event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4564604, (71,548), root:(146,643),
state 0x84, keycode 10 (keysym 0x7c, bar), same_screen YES,
XLookupString gives 1 bytes: (1c)
KeyPress event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4564932, (71,548), root:(146,643),
state 0x84, keycode 11 (keysym 0x40, at), same_screen YES,
XLookupString gives 1 bytes: (00)
XmbLookupString gives 1 bytes: (00)
XFilterEvent returns: False
KeyRelease event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4564979, (71,548), root:(146,643),
state 0x84, keycode 11 (keysym 0x40, at), same_screen YES,
XLookupString gives 1 bytes: (00)
KeyPress event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4565322, (71,548), root:(146,643),
state 0x84, keycode 12 (keysym 0x23, numbersign), same_screen YES,
XLookupString gives 1 bytes: (23) #
XmbLookupString gives 1 bytes: (23) #
XFilterEvent returns: False
KeyRelease event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4565369, (71,548), root:(146,643),
state 0x84, keycode 12 (keysym 0x23, numbersign), same_screen YES,
XLookupString gives 1 bytes: (23) #
KeyRelease event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4566586, (71,548), root:(146,643),
state 0x84, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
KeyRelease event, serial 24, synthetic NO, window 0xe1,
root 0x3e, subw 0x0, time 4566586, (71,548), root:(146,643),
state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XLookupString gives 0 bytes:
Does anyone have any ideas? Thanks.
Andrew Blake
--
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/
