X1 keyboard input not accepted

Recently my keyboard input is not accepted. There is clicking when I tap the keys, but no input is taken. The soft keyboard works as expected. Is there a setting I tweaked somewhere?

I experienced the same proble. Mine X1CT was bought in January. The problem came today.
When the keyboard is not working, the touch screen is not working too.
I guess it has something to do with the external display, and the hinge between laptop display and laptop body.
Normally I use only the external display. In the Fn+F7 option, I chose the last one (Second Screen only).
When I had this problem, the only way to make it work is to adjust the lapto screen angle. Sometimes both screens will be turn on, then it becomes normal again.
Please help. 

Similar Messages

  • I have a new mac book pro (sept 2014) and am suddenly stuck on the log-in screen. Keyboard input not working to enter my password. Already tried a basic restart and a cmmnd/ cntrl/ pwr troubleshoot to no effect.

    I have a new mac book pro (sept 2014) and am suddenly stuck on the log-in screen. Keyboard input is not working to enter my password. Seems to be a log in issue as keyboard works for forced troubleshooting. (And b/c when I first noticed the problem, I was able to enter my log in password but then everything sort of froze. Now, no ability to enter the password.) Already tried a basic restart and a cmmnd/ cntrl/ pwr troubleshoot to no effect.

    Reset PRAM:   http://support.apple.com/kb/PH14222
    Start up in Safe Mode.
    http://support.apple.com/kb/ph14204
    A new Mac is in warranty for 1 year from the date of purchase.
    A new Mac comes with 90 days of free tech support from AppleCare.
    AppleCare: 1-800-275-2273
    Call AppleCare or take it to the Apple store to have it checked out.
    Genius Bar reservation
    http://www.apple.com/retail/geniusbar/
    Best.

  • Kazakh keyboard input not works

    Hi.
    I'm can't figure out trouble with kazakh(cyrillic) input to text controls in Flex4.
    I'm embedded unicode fonts, and "Copy->Paste" kazakh text from notepad into flash app works fine!
    But i need to keyboard input. In my case ordinar cyrillic letters inputs normal, but kazakh-specific
    letters (located in keyboard's 1234 and 7890 keys) not works - ? symbol displays.
    Please, anyone help me. I'm wasting 2 weeks in attempt to resolve it.
    P.S: FlexSDK 4.0.0.12321, FP 10.0.42.34, OS Windows.

    When you paste and it works, take the string and look at the charCodeAt() for each character in the string.
    Then when you type, see if the keyDown event is reporting the same charCode or not.
    Another test is to verify that your browser can allow those characters when typed into an HTML INPUT tag.
    Hi!
    When i'm pasting kazakh letters into textInput, flexApp shows correct charCodes, e.g.:
    әіңғүұқөһ -> 1241 1110 1187 1171 1199 1201 1179 1257 1211
    but when i'm typing this letters from keyboard, flex shows these charCodes:
    ?і??????? -> 63 1110 63 63 63 63 63 63 63
    (cyrillic-kazakh letters located in place of 2,3,4,5,8,9,0,-,= symbols of keyboard, on simple click - lowercase, with ShiftKey - uppercase).
    testing app code:
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                   xmlns:s="library://ns.adobe.com/flex/spark"
                   xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
        <fx:Script>
            <![CDATA[
                import mx.controls.Alert;
                protected function richeditabletext1_keyDownHandler(event:KeyboardEvent):void
                protected function rt1_keyUpHandler(event:KeyboardEvent):void
                    ttt.text = "";               
                    for (var i:uint = 0; i<rt1.text.length; i++){
                        ttt.text = ttt.text+" "+ rt1.text.charCodeAt(i);
            ]]>
        </fx:Script>
        <fx:Style>
            @namespace s "library://ns.adobe.com/flex/spark";
            @namespace mx "library://ns.adobe.com/flex/mx";
            @font-face {
                src: url("arialuni.ttf"); /* Embed from file */
                fontFamily:"Thai_font";            
                /*unicodeRange:"Cyrillic";*/
                unicodeRange: U+0400-04F9;
                cff-hinting:none;
                embeddAsCFF:true;
            .test{
                font-family:Thai_font;
        </fx:Style>
        <s:TextInput id="ttt" width="100%" fontFamily="Arial Unicode MS"/>
        <s:TextInput id="rt1" x="562" y="243" text="RichEditableText" width="100%" height="500" enabled="true"
                            editable="true"  fontSize="18" keyDown="richeditabletext1_keyDownHandler(event)"
                            keyUp="rt1_keyUpHandler(event)"
                            direction="ltr"
                            styleName="test"/>
    </s:Application>

  • Keyboard input not working at boot

    Hello --
    I don't get keyboard input for ~30 seconds at boot, and I'm not sure why. I'm using a hand-rolled kernel with no initrd, though when I use the stock Arch kernel with initrd it does the same thing. According to my kernel logs, the keyboard is recognized before the root filesystem is mounted (and it appears to be PS2, not USB), and from reading the rc scripts, little or nothing happens after the ttys are started.
    udev starts before the root fs is mounted, and when root is fscked at boot, I don't encounter this problem. Therefore I think udev is at fault. Via I can't find any information on telling udev to deal with the keyboard earlier.
    Any ideas on how to fix this? Other than putting "sleep 30" in my rc scripts, that is.

    Sorry, I wasn't being very clear.
    I'm using a laptop, and lsusb doesn't report anything except the buses themselves. Therefore I concluded that my keyboard is not a USB keyboard, as I mentioned above.
    This is booting to a tty console, not to X, so it can't be a KDE issue. And I have full control of my keyboard with GRUB; it's just the kernel that hesitates to acknowledge its existence.

  • Keyboard Input not Registerin​g

    I recently upgraded to a Q10 from my 9930 and I've been encountering an issue which is more than frustrating.
    I will boot up the phone and, not too long afterwards, the phone will not be registering keyboard input
    (search won't work from home screen and can't enter text into any form).
    I've tried running a keyboard test with the BBVE software and it registers all keys. Doing a quick restart on the phone fixes the issue temporarily, but it reappears almost immediately. 
    Has anybody encountered this issue before and have some advice?

    If restarting your phone corrects the issue only temporarily, it's probably related to software. Your first step will be to reload your OS using BlackBerry Link. Plug your phone in to your PC and open Link. Click Backup and Restore and do a backup of your phone. Once that's complete, once again click Backup and Restore and restore that backup to your phone.
    If that doesn't correct the issue, take your phone back to your carrier for a warranty replacement; you can then restore the backup you created to your new replacement phone.
    I hope that helps you.  
    - If my response has helped you, please click "Options" beside my post and mark it as solved. Clicking the "thumbs up" icon near the bottom of my response would also be appreciated.

  • TS1569 Brand new wireless aluminum keyboard will not accept passcode

    .......... to pair with brand new macbook air. Apple Care support can't figure this out. Just tried a second, identical keyboard in two days. Same issue. First keyboard worked flawlessly with mid 2010 macbook pro. I'm ******!

    I just does not accept that it should be nessecarry to use a usb keyboard when buying a brand new mac!
    And luckily I managed to solve this in the end
    My setup was is with a keyboard that was previously paired worth my MBP, and I tried a lot of things, but what did it in the end was this:
    First I unpaired the keyboard from the MBP using http://support.apple.com/kb/HT1809?viewlocale=en_US&locale=en_US. Only, this time I ignored the first step which reads: "Press and release the On/Off switch on the wireless keyboard to turn it off." Thinking of it, how would the the keyboard know that it is unpaired, if it is turned off?
    The 2 thing I did differently this time was that I did not power on the keyboard until it actually said so on the screen. This means that I powered on the Mini, waited until I had selected the language using the Trackpad, waited until the "Connect Keyboard" dialog appeared on the screen. Then I turned on the keyboard in pairing mode...
    That's basically what I did to be successful! Hope it will help somebody else

  • Why values selected for a h:selectOneMenu via keyboard are not accepted?

    Hi,
    I have a h:selectOneMenu in a jspx page. When i run the page on IE6 and I select a value using the keyboard, the value selected is not accepted. But when i run the same page on Mozilla Firefoz 1.5 and select a value through the keyboard it works..
    Can someone help me on how to get the value wen i select through the keyboard on IE6.
    Thanks
    Meenackshi

    Tell IE to use the Sun VM.

  • Safari 7.1 blocks all keyboard input in Flash app

    Safari 7.1 on OSX 10.9.5 blocks any and all keyboard input for FlashPlayer applications!! Everything worked fine until the upgrade to Safari 7.1 and OSX 10.9.5. Tried FlashPlayer 14 and the latest 15 -- still no keyboard input, not even in debug mode (I'm a developer of enterprise apps for browsers).
    The same app still works just fine in Firefox and Google Chrome! Is this just a mishap on Apple's side? Or just another hit to kill off the most productive computer language I've ever used (and I used Apple's own Objective-C as well)??
    Come on Apple! I love you guys and use your products a lot, but is this really necessary for the most powerful and valuable company in the world -- to hurt a language with such tricks that doesn't do you any harm at all?? This makes you look more like the "PC guy" from your own former commercials (instead of the lovable "Mac guy") ...

    From the menu bar, select
               ▹ System Preferences… ▹ Flash Player ▹ Advanced
    and click Delete All. Close the preference pane.
    From the Safari menu bar, select
              Safari ▹ Preferences... ▹ Privacy ▹ Remove All Website Data
    and confirm. Test.

  • Firefox and Thunderbird are suddenly not accepting keyboard input

    Keyboard shortcuts still work just input in any kind of input field fails so I can still use ctrl+C / CTRL+V to somewhat use firefox and Thunderbird But all input fields are completely unresponsive to keyboard input
    The problem suddenly arose while I was browsing.
    I have the same issue on all program's based on the Gecko engine and I confirmed them so far in Firefox, waterfox, instantbird, thunderbird and fossamail. However chromium / windows / basically everythign n
    To fix it I tried the following:
    Restarting firefox
    Restarting firefox in savemode
    Rebooting
    Changing the keyboard layout in windows
    Using a different keyboard
    Again rebooting
    Pressing F7 to check for caret mode which was disabled
    pressing winkey + F9 (Whatever that does)
    I am running windows 8.1(x64)

    Solved, Changing the keyboard layout again and rebooting fixed it. I tried using the on screen keyboard which worked so I changed the keyboard layout again and rebooted and now it works just fine. I still wonder what caused a Gecko wide issue like this?

  • Firefox not responding to keyboard input

    I'm having issues with Firefox temporarily no longer responding to keyboard input.
    I have two machines, both running Windows 7. On my laptop, I never have any issues but on my desktop, I find that Firefox sometimes blocks keyboard input. It will allow me to enter one character in any text field, and no more. Any further input is ignored. This applies to the address bar, the search box and any text fields in the displayed web page, in any tab. All keyboard navigation seems to also be ignored.
    I've tried Reset Firefox and Safe Mode, they don't appear to change anything. I've also tried uninstalling Synergy and changing from my regular English-International keyboard layout to US English, but this still seems to occur. I am also running Workrave which can interrupt keyboard input, but since I can add 1 character, I suspect that Workrave is not the problem.
    Sometimes it can seemingly be unblocked by pressing Start+F9, CTRL+SHIFT+ESC, restarting firefox or opening a new tab, but this seems to only be a temporary solution, the problem soon reoccurs. This bug has been present for some time, I first noticed it in v28 (although it may be even older), I am currently using v31.
    One thing I've noticed is that it never occurs until after my screen has been locked at least once.
    The trouble-shooting information attached will not be entirely accurate because I'm using my laptop to type this - Firefox is not accepting keyboard input right now on my desktop! However, the two environments are similar.
    Thanks, Tadhg

    Some have reported that pressing F9 and the Windows key simultaneously one or more times has worked to fix issues with the keyboard not working.

  • Server 2012 not accepting inputs either via console or RDP

    Hello Experts,
    I have a server 2012 standard running in a physical box with 3 virtual machines running in hyper-v session. For sometime now, i have been running into strange issues where it does not accept input. I tried via RDP, console; neither method worked. It still
    holds AD and file server role. It was all working good and driving me into issues for some time now.
    It does not accept inputs via keyboard or mouse either from console or RDP. All resources such as file share, virtual machine are accessible from network. I can logon to server via console or RDP for 3 to 5 min right after server has been hard restarted
    and again it stops accepting inputs.
    Can someone help me out work around this issue as i am new to server 2012 and not sure what goes in error.
    Thanks.

    Hi koneska,
    Did you install any software recently? Please try to unistall the new installed software and if you have AV soft disable the AV soft then try again.
    Regards.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Thunderbird 24.6.0 suddenly stops accepting keyboard input in the middle of typing a message

    On a system running Debian Testing (kernel version 3.13.10-1), at times Thunderbird 24.6.0 suddenly stops accepting keyboard input in the middle of typing a message. Some times, it will not accept keyboard input from the time a new message window opens (both from click Write or Reply).
    Regardless of when the problem starts, I can still copy text from another source and paste it into the message, and I can still send the message.
    Sometimes, the problem will clear up itself after a few minutes, meaning I can suddenly start typing in the open message window, but sometimes not, and I will have to close the message window and restart Thunderbird or reboot the system.

    Tasks: 290 total, 1 running, 242 sleeping, 47 stopped, 0 zombie
    %Cpu(s): 1.0 us, 0.3 sy, 0.0 ni, 98.2 id, 0.4 wa, 0.0 hi, 0.0 si, 0.0 st
    KiB Mem: 8101216 total, 6406932 used, 1694284 free, 46440 buffers
    KiB Swap: 8388604 total, 280476 used, 8108128 free. 2714812 cached Mem
    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    9498 pete 20 0 905252 171068 60844 S 4.3 2.1 0:36.22 chrome
    1207 root 20 0 301372 31896 12592 S 1.0 0.4 40:04.04 Xorg
    7904 pete 20 0 796904 75304 25496 S 1.0 0.9 0:54.16 chrome
    7349 pete 20 0 1215536 345724 116416 S 0.7 4.3 3:29.51 chrome
    7539 pete 20 0 879076 128096 26512 S 0.7 1.6 1:51.35 chrome
    7670 pete 20 0 826900 70488 23812 S 0.7 0.9 0:13.12 chrome
    7793 pete 20 0 872564 135004 68628 S 0.3 1.7 0:13.74 chrome
    7845 pete 20 0 811680 80360 23580 S 0.3 1.0 0:06.61 chrome
    7877 pete 20 0 812032 79888 23668 S 0.3 1.0 0:08.91 chrome
    9666 pete 20 0 23796 1808 1136 R 0.3 0.0 0:00.01 top
    22931 pete 20 0 1094964 186504 22808 S 0.3 2.3 14:28.61 thunderbird
    1 root 20 0 193016 2860 1260 S 0.0 0.0 0:03.67 systemd
    2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd
    3 root 20 0 0 0 0 S 0.0 0.0 0:22.21 ksoftirqd/0
    5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
    7 root 20 0 0 0 0 S 0.0 0.0 1:09.66 rcu_sched
    8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
    9 root rt 0 0 0 0 S 0.0 0.0 0:00.34 migration/0
    10 root rt 0 0 0 0 S 0.0 0.0 0:00.58 watchdog/0
    11 root rt 0 0 0 0 S 0.0 0.0 0:00.58 watchdog/1
    12 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/1
    13 root 20 0 0 0 0 S 0.0 0.0 0:13.05 ksoftirqd/1
    15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/1:0H
    16 root rt 0 0 0 0 S 0.0 0.0 0:00.50 watchdog/2
    17 root rt 0 0 0 0 S 0.0 0.0 0:00.02 migration/2
    18 root 20 0 0 0 0 S 0.0 0.0 0:04.84 ksoftirqd/2
    20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/2:0H
    21 root rt 0 0 0 0 S 0.0 0.0 0:00.52 watchdog/3
    22 root rt 0 0 0 0 S 0.0 0.0 0:00.03 migration/3
    23 root 20 0 0 0 0 S 0.0 0.0 0:11.02 ksoftirqd/3
    25 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/3:0H
    26 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
    27 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
    28 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
    29 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback
    30 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd
    31 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
    32 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
    34 root 20 0 0 0 0 S 0.0 0.0 0:00.11 khungtaskd
    35 root 20 0 0 0 0 S 0.0 0.0 3:41.37 kswapd0
    36 root 25 5 0 0 0 S 0.0 0.0 0:00.00 ksmd
    37 root 39 19 0 0 0 S 0.0 0.0 0:00.00 khugepaged
    38 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
    39 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
    44 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kthrotld
    46 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 deferwq
    86 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ata_sff
    88 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_0
    89 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_1
    90 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_2

  • What can I do about a 2008 iMac that does not accept any input, thus blocking entry of password at startup?

    My 2008 iMac (20 inch) often freezes. Now it will not accept any input on startup.  I type in my password, but it will not accept any characters I enter.  The blinking line just continues to blink.  It will not acknowledge my keyboard, mouse or trackpad.  I have done a forced reboot and a force reboot combined with subsequently disconnecting the power cord and then restarting.  No response from either step.  What can I do?
    Thanks.

    Glad it is working for you.
    Have a look at these two articles they may help if it occurs again.
    http://support.apple.com/kb/ht3964
    http://support.apple.com/kb/HT1379

  • In iCal - I keep getting the error message " This calendar was created by Mail" and it will not accept any input; why..??

    In iCal - I keep getting the error message “ This calendar was created by Mail” and it will not accept any input; why..??

    use Disk Utility and Verify Permisions then fix and Verify Disk and fix, this should fix it.

  • Terminal window blinking cursor will not accept keyboard entry

    Have SunBlade100 w/ Solaris8.
    This is probably a dumb beginner question...
    When I enter certain commands at the terminal window - in this particular case
    # cat /dev/cua/a
    and I hit <return> the cursor skips to the next line, and
    continues blinking , and will not accept any keyboard entries.
    1. What is the significance of this? Is the cursor waiting further action, and if so, what?
    2. How do I get back to the prompt?
    3. Under this condition, is it safe to exit the terminal window by closing from the Window menu? (I can't type "exit" because the cursor won't accept keyboard entries, and Help for "closing the terminal" warns against closing from the Window menu because any background processes will not be terminated (and this may cause problems).
    Thanks in advance for any info on this.

    Thanks again for the info. <control>+C was exactly what I was looking for. It's coming back to me now-- the last time I had contact w/ UNIX was back in '85 at UC Berkeley (no GUI's back then!).
    I'm assuming that <control>+C is a graceful (i.e. relatively harmless way to exit the command.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Maybe you are looking for