New answers tagged keyboard
Key boards are designed with a matrix pattern of rows and columns. The keyboard has a micro-controller that scans those rows and columns to see what button(s) are pressed. Your best bet is to pull the keys and (I'm assuming) the rubber membrane and clean it and the board with rubbing alcohol. Looks like a hardware issue to me.
I don't have enough reputation to comment on this so i made it an answer I bet it has to do with your hard disk's heads or MBR and your problem happens a lot actually. Because of different standards some BIOS could read from an address above the MBR which could cause your problem and what will solve that is to try using parted and some W.D. drives have ...
In Preferences > Profiles > Keys. Create a Key combination "⌥ ← Delete" and have it Send Hex Codes: 0x1B 0x08. It will delete one word backwards using a non-alphanumeric character as delimiter.
From zsh, you could do something like: cmd="stty rows $LINES cols $COLUMNS; stty '$(stty -g)'; bash" STTY='raw -echo' cat > typescript.in | script -c "$cmd" Then you'd have what you typed in typescript.in and the output in typescript.
On OpenSuse 13.x with KDE, this worked for me: install numlockx Add Custom Shortcut: Custom Shortcuts -> Edit -> New -> Global Shortcut -> Command/URL: Action Name: NumLockOn Comment: Keep numlock on Trigger: set to NumLockk Action-> Command/URL: sh -c 'sleep 0.5;numlockx on' Hit apply (done) If NumLock needs to be enabled because its off, just use % ...
The code ^[[6~ is generated by Page Down key. You can check it at the command-line in bash by hitting Ctrl-v + Pg Dn.
In my grub.cfg file their is this term - console.keymap=us in every linux boot command line. The 3.14.27-100 kernel was part of a complete upgrade with yum. I don't know if this term was always there or if it was part of a revamped grub.cfg file done with the new kernel install. But here is what solved the problem. I just changed the term to: ...
Top 50 recent answers are included