Re: x keyboard with most keys dead since update -- faq answer 3.2 no help

[Blake Thomas Andrew <blakethomasandrew at gmail dot com>]

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
<blakethomasandrew@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 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
> (--) 5 mouse buttons found
> (--) Setting autorepeat to delay=500, rate=31
> (--) winConfigKeyboard - Layout: "0000080A" (0000080a)
> (--) 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.turney@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 reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/