Deleted my keyboard layouts

(hope this is the right category..)
I wanted to make some space on my HD and used an app to delete unneeded keyboard layouts - I deleted them all..
Now I'm unable to type on my MBP's keyboard. So I googled a little etc.. imported keyboard layouts from another Mac..
Problem starts here: When I want to add the keyboard layouts to /system/library/keyboard layouts I need to type my pw to modify the folder, but i _cant type_ T_T tried copy&paste which doesn't work. argh.. ("ah! still got the OSX install CD.." - also desn't work - need to type pw to install..)
Anyone know how I can solve this?
thanks in advance

Better just reinstall your OS so you have a full working system.
In the future don't delete any keyboard layouts, the space they use is trivial.

Similar Messages

3.4 deleted my custom keyboard layout settings

Hi,
just a nasty bug report. On all my Macs (iMac 27" early 2009 and mid 2011; MPB 15" early 2008 - all running 10.8.2) Aperture 3.4 update deleted my custom keyboard layout setting. It is just gone....
You better make backup before you update. I wonder what I will discover next....
Seems to me like Aperture will never be a great piece of software...

How did you create the custom keyboard layout? Using a plug-in? Or do mean the custom command settings? My custom command settings are still there. The presets are stored in the User library if you need to restore them.
~/Library/Application Support/Aperture/Command Sets/My Commands.apcommands
If you used plug-ins to configure Aperture, check out if they are still compatible. The recent version accepts only sandboxed plug-ins:
Aperture 3.4 and later: Some third-party plug-ins are no longer compatible
Regards
Léonie

How can I get Final Cut 7 to remember my customized keyboard layout?

Hi everyone, I'm new to this community, my name is Flavio, from Argentina.
I'm on a Mac Book Pro Intel Core Duo 2, using Final Cut 7 and I'm using a customized keyboard layout (1 for zoom in, 2 for zoom out), but everytime I launch the application I have to go to Tools>Keyboard Layout to change it, is there a way to tel the ap to launch that layout almays?
Thanks!

It works for me without doing anything special. You might try deleting your fcp preferences
https://discussions.apple.com/docs/DOC-2491
If that doesn't solve it, describe exactly what your doing to customize the keyboard.
I assume if you do a "save keyboard layout" from the tools menu: keyboard layout after customizing the keyboard and then load keyboard layout after relaunching fcp, that at least works.

Input menu changing my default keyboard layout-again. Grrrr!

This same issue had come up years ago, and I no longer remember with certainty how it was fixed. It just geared up its ugly head again. Ever since I can remember, I've been using a custom keyboard layout, which I arbitrarily labeled "Cantabria", that lets me type in seven languages with an absolute minimum of key combos. I only need a different keyboard layout for Cyrillic (Russian).
The problem is that, in the past few days or weeks, the system arbitrarily changes my Input Menu to reflect one of the two US English keyboards as the active one, either US or US Extended. I can't see a pattern. It just happens. The Menu Input key combinations are duly disabled, so it's not my accidentally hitting Command+Space.
I thought the solution had been simply to UNcheck both US keyboard options in International, but now it seems you can't do that. You have to have at least one of them selected.
Any ideas on how to stop this annoyance will be much appreciated.
Thanks in advance.

To my stunned amazement, I just found this other thread from last September with the same issue. I had no memory of having posted then and I still have no independent recollection of it. Major senior moment, darn!
https://discussions.apple.com/message/16121983#16121983
Strange that back then I was able to unselect both US English keyboard layouts and now I can't, on the same machine and same OS build. I'll try deleting the files BDAqua mentions in that other thread.
In attenuating defense of my brain malfunction I can only offer that the other thread is dated the same day my second grandson was born. My mind was obviously elsewhere.

[Solved]Keyboard layout screwed up and some keys don't work

After I reinstalled xorg-server 1.5.3-1 and installed xf86-input-evdev 2.0.1-1 and xf86-input-keyboard 1.3.1-1 some of my keys don't work and keyboard layout screwed up. I had finnish (fi) layout, but now it's "us". Arrows, insert- delete- home- end- pg up- pg down- print screen- scroll lock- pause- keys don't work. All characters behind Alt Gr + "" don't work either.
How to fix this?
Last edited by Sotamarsu (2008-11-08 13:57:25)

brother fixed it with next code
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>

<match key="info.capabilities" contains="input.keys">


<merge key="input.x11_options.XkbRules" type="string">base</merge>
<merge key="input.x11_options.XkbModel" type="string">evdev</merge>
<merge key="input.x11_options.XkbLayout" type="string">fi</merge>
<append key="input.x11_options.XkbOptions" type="strlist">altwin:menu</append>

</match>
</device>
</deviceinfo>
Last edited by Sotamarsu (2008-11-08 13:59:18)

MSI, please stop using non-standard keyboard layouts.

God dam it MSI, why do you insist on messing with layout of the bottom row of the keyboard?
You get everything else right, but for some reason when it comes to the bottom row of keys you want to say "Industry standards? 20 years of tradition? Fack that, we're gonna move things around for no facking reason."
Explain to me why you feel the need to put a superfluous "\" key on the keyboard to the right of the space bar. Nobody wanted that, nobody was asking for that, nobody needs that. Why the hell did you do that?
Explain why the Menu key is missing in action.
Explain why you put the Windows key on the wrong side. And while you're at it, explain why you thought this clusterfack of having that second "\" key there in combination with the missing menu key being not where it is on top of the Windows key being in the wrong place was a good idea.
Bottom row of a standard keyboard layout goes like this:
Ctrl, Fn, Alt, Win, Space bar, Alt, Win, Menu, Ctrl.
MSI layout goes like.
Ctrl, Fn, Alt Space Bar, \, Alt Gr, Win, Ctrl!
WHY?!
MSI seems to think that having the keys in the right place so my fingers will know where they are without having to learn key placement all over again is a horrible idea. Instead they seem to think that my fingers should need to relearn the god dam keyboard all over again for no reason at all.
But hey, at least the kept the numpad the same, right?
GOD DAM IT MSI!
Aparantly MSI logic works like this:
Everyone uses the numpad.
Nobody uses the trackpad to game.
Delete that numpad that everyone uses, insert fancy trackpad that nobody will use.
Profit?
What the hell are you people smoking?
Seriously, when is the last time you gamed on a PC with anything other than a mouse in your right* hand? Do you ever use the trackpad when you game? Ever? I own two laptops and I never, ever use the useless trackpad. I hate trackpads. First thing I do when I buy a new laptop? I plug in a mouse. Second thing I do? Disable the god dam trackpad.
*Some left-handed use of mice can occur. See nearest lefties for details. May contain nuts. For external use only.

I had a Gateway FX years ago that was a great laptop, but the "fn" key was at the bottom left instead of ctrl. I used that laptop for years and I was never able to become accustomed to it for gaming (group select ctrl+# ffs) or word processing, so I feel your pain.
That being said, you should be able to re-bind your keys without any problem, and possibly pop off the keys themselves and move them to their new locations if they're the same size and you like that consistency. You can rebind via the registry, or certain bios, or w/ a third party application.
The track pad is essential if you've got limited space and/or aren't a twitch gamer. For non-real time games, there is hardly any advantage to using a mouse over a good track pad.

[E17] lock and keyboard layout problems when suspend

Hello,
I just installed E17 on my Dell Vostro laptop. The main problem I have is related to the suspend mode.
In settings > screen > screen lock, I enabled the option "lock on suspend" and the keyboard layout is selected to "be (default, basic)" (I have a belgian keyboard).
When I use the menu system > suspend, the screen is locked. But when I suspend my laptop by closing the lid (I see the power light indicator blinking on the side, so it's suspended) the screen is not locked when I open it.
Also related to the suspend mode. The layout is set to belgian (in the screen config as explained above but also in vconsole.conf and in /etc/X11/xorg.conf.d/10-keyboard.conf). When I put the luks decryption key or when E17 starts at boot, I have the right layout. However when I resume the laptop after being suspended, the layout is switched to qwerty (en_us I guess).
Any idea why ?
Thank you
PS: this problem is maybe more related to E17 than to Archlinux but I haven't found any forum about enlightenment. If you think I have better chances somewhere else, let me know.

I was having problems with E17 after a fresh install (mixer problem, key bindings, etc), and I fixed it by deleting the configuration files at
~/.e
as the wiki says.

[SOLVED] Keyboard layout problems

Hi community,
I fresh installed arch linux and I rly like it. After playing a little around and installing the awesome wm I can't set the croatian keyboard layout.
My xorg.config file:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "logicd"
Option "XkbLayout" "hr"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Arnos Instruments F-417"
HorizSync 24.0 - 80.0
VertRefresh 49.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6600 GT"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
My Xorg.0.log file:
[ 2186.778]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 2186.778]
X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
[ 2186.778] X Protocol Version 11, Revision 0
[ 2186.778] Build Operating System: Linux 2.6.34-ARCH x86_64
[ 2186.778] Current Operating System: Linux arch 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010 x86_64
[ 2186.778] Kernel command line: root=/dev/sda5 ro
[ 2186.778] Build Date: 21 June 2010 12:01:49PM
[ 2186.778]
[ 2186.779] Current version of pixman: 0.18.2
[ 2186.779] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2186.779] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2186.779] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 22 13:23:50 2010
[ 2186.779] (==) Using config file: "/etc/X11/xorg.conf"
[ 2186.779] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2186.779] (==) ServerLayout "Layout0"
[ 2186.779] (**) |-->Screen "Screen0" (0)
[ 2186.779] (**) | |-->Monitor "Monitor0"
[ 2186.779] (**) | |-->Device "Device0"
[ 2186.779] (**) |-->Input Device "Keyboard0"
[ 2186.779] (**) |-->Input Device "Mouse0"
[ 2186.780] (**) Option "Xinerama" "0"
[ 2186.780] (==) Automatically adding devices
[ 2186.780] (==) Automatically enabling devices
[ 2186.780] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2186.780] Entry deleted from font path.
[ 2186.780] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2186.780] Entry deleted from font path.
[ 2186.780] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 2186.780] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 2186.780] (WW) Disabling Keyboard0
[ 2186.780] (WW) Disabling Mouse0
[ 2186.780] (II) Loader magic: 0x7ce880
[ 2186.780] (II) Module ABI versions:
[ 2186.780] X.Org ANSI C Emulation: 0.4
[ 2186.780] X.Org Video Driver: 7.0
[ 2186.780] X.Org XInput driver : 9.0
[ 2186.780] X.Org Server Extension : 3.0
[ 2186.786] (--) PCI:*(0:1:0:0) 10de:00f1:0000:0000 nVidia Corporation NV43 [GeForce 6600 GT] rev 162, Mem @ 0xf8000000/16777216, 0xe0000000/268435456, 0xf9000000/16777216, BIOS @ 0x????????/131072
[ 2186.787] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2186.787] (II) LoadModule: "extmod"
[ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 2186.787] (II) Module extmod: vendor="X.Org Foundation"
[ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.787] Module class: X.Org Server Extension
[ 2186.787] ABI class: X.Org Server Extension, version 3.0
[ 2186.787] (II) Loading extension MIT-SCREEN-SAVER
[ 2186.787] (II) Loading extension XFree86-VidModeExtension
[ 2186.787] (II) Loading extension XFree86-DGA
[ 2186.787] (II) Loading extension DPMS
[ 2186.787] (II) Loading extension XVideo
[ 2186.787] (II) Loading extension XVideo-MotionCompensation
[ 2186.787] (II) Loading extension X-Resource
[ 2186.787] (II) LoadModule: "dbe"
[ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 2186.787] (II) Module dbe: vendor="X.Org Foundation"
[ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.788] Module class: X.Org Server Extension
[ 2186.788] ABI class: X.Org Server Extension, version 3.0
[ 2186.788] (II) Loading extension DOUBLE-BUFFER
[ 2186.788] (II) LoadModule: "glx"
[ 2186.788] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2186.813] (II) Module glx: vendor="NVIDIA Corporation"
[ 2186.813] compiled for 4.0.2, module version = 1.0.0
[ 2186.813] Module class: X.Org Server Extension
[ 2186.813] (II) NVIDIA GLX Module 256.35 Wed Jun 16 19:10:31 PDT 2010
[ 2186.813] (II) Loading extension GLX
[ 2186.813] (II) LoadModule: "record"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 2186.814] (II) Module record: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.13.0
[ 2186.814] Module class: X.Org Server Extension
[ 2186.814] ABI class: X.Org Server Extension, version 3.0
[ 2186.814] (II) Loading extension RECORD
[ 2186.814] (II) LoadModule: "dri"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 2186.814] (II) Module dri: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.814] ABI class: X.Org Server Extension, version 3.0
[ 2186.814] (II) Loading extension XFree86-DRI
[ 2186.814] (II) LoadModule: "dri2"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2186.814] (II) Module dri2: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.2.0
[ 2186.815] ABI class: X.Org Server Extension, version 3.0
[ 2186.815] (II) Loading extension DRI2
[ 2186.815] (II) LoadModule: "nvidia"
[ 2186.815] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2186.816] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2186.816] compiled for 4.0.2, module version = 1.0.0
[ 2186.816] Module class: X.Org Video Driver
[ 2186.816] (II) NVIDIA dlloader X Driver 256.35 Wed Jun 16 18:45:02 PDT 2010
[ 2186.816] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2186.816] (++) using VT number 7
[ 2186.820] (II) Primary Device is: PCI 01@00:00:0
[ 2186.820] (II) Loading sub module "fb"
[ 2186.820] (II) LoadModule: "fb"
[ 2186.820] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2186.821] (II) Module fb: vendor="X.Org Foundation"
[ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2186.821] (II) Loading sub module "wfb"
[ 2186.821] (II) LoadModule: "wfb"
[ 2186.821] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2186.821] (II) Module wfb: vendor="X.Org Foundation"
[ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2186.821] (II) Loading sub module "ramdac"
[ 2186.821] (II) LoadModule: "ramdac"
[ 2186.821] (II) Module "ramdac" already built-in
[ 2186.821] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 2186.821] (==) NVIDIA(0): RGB weight 888
[ 2186.821] (==) NVIDIA(0): Default visual is TrueColor
[ 2186.821] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2186.821] (**) NVIDIA(0): Option "TwinView" "1"
[ 2186.822] (**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
[ 2186.822] (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
[ 2186.822] (**) NVIDIA(0): Enabling RENDER acceleration
[ 2186.822] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 2186.822] (II) NVIDIA(0): enabled.
[ 2188.363] (II) NVIDIA(0): NVIDIA GPU GeForce 6600 GT (NV43) at PCI:1:0:0 (GPU-0)
[ 2188.363] (--) NVIDIA(0): Memory: 131072 kBytes
[ 2188.363] (--) NVIDIA(0): VideoBIOS: 05.43.02.39.00
[ 2188.363] (II) NVIDIA(0): Detected AGP rate: 8X
[ 2188.363] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 2188.363] (--) NVIDIA(0): Connected display device(s) on GeForce 6600 GT at PCI:1:0:0:
[ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0)
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0)
[ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0): 400.0 MHz maximum pixel
[ 2188.363] (--) NVIDIA(0): clock
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): 155.0 MHz maximum pixel clock
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): Internal Single Link TMDS
[ 2188.363] (**) NVIDIA(0): TwinView enabled
[ 2188.363] (II) NVIDIA(0): Display Devices found referenced in MetaMode: CRT-0, DFP-0
[ 2188.364] (II) NVIDIA(0): Assigned Display Devices: CRT-0, DFP-0
[ 2188.364] (II) NVIDIA(0): Validated modes:
[ 2188.364] (II) NVIDIA(0):
[ 2188.364] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
[ 2188.364] (II) NVIDIA(0): Virtual screen size determined to be 3200 x 1080
[ 2188.364] (--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
[ 2188.364] (--) NVIDIA(0): option
[ 2188.364] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 2188.364] (--) Depth 24 pixmap format is 32 bpp
[ 2188.365] (II) NVIDIA(0): Initialized AGP GART.
[ 2188.373] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 2188.373] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 2188.373] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 2188.373] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 2188.373] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 2188.373] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 2188.373] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 2188.373] (II) NVIDIA(0): Config Options in the README.
[ 2188.373] (II) NVIDIA(0): Setting mode
[ 2188.373] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
[ 2188.613] (II) Loading extension NV-GLX
[ 2188.657] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 2188.659] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 2188.659] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 2188.659] (==) NVIDIA(0): Backing store disabled
[ 2188.659] (==) NVIDIA(0): Silken mouse enabled
[ 2188.660] (**) NVIDIA(0): DPMS enabled
[ 2188.660] (II) Loading extension NV-CONTROL
[ 2188.661] (II) Loading extension XINERAMA
[ 2188.661] (II) Loading sub module "dri2"
[ 2188.661] (II) LoadModule: "dri2"
[ 2188.661] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2188.661] (II) NVIDIA(0): [DRI2] Setup complete
[ 2188.661] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 2188.661] (==) RandR enabled
[ 2188.661] (II) Initializing built-in extension Generic Event Extension
[ 2188.661] (II) Initializing built-in extension SHAPE
[ 2188.661] (II) Initializing built-in extension MIT-SHM
[ 2188.661] (II) Initializing built-in extension XInputExtension
[ 2188.661] (II) Initializing built-in extension XTEST
[ 2188.661] (II) Initializing built-in extension BIG-REQUESTS
[ 2188.661] (II) Initializing built-in extension SYNC
[ 2188.661] (II) Initializing built-in extension XKEYBOARD
[ 2188.661] (II) Initializing built-in extension XC-MISC
[ 2188.661] (II) Initializing built-in extension SECURITY
[ 2188.661] (II) Initializing built-in extension XINERAMA
[ 2188.661] (II) Initializing built-in extension XFIXES
[ 2188.661] (II) Initializing built-in extension RENDER
[ 2188.661] (II) Initializing built-in extension RANDR
[ 2188.661] (II) Initializing built-in extension COMPOSITE
[ 2188.661] (II) Initializing built-in extension DAMAGE
[ 2188.664] (II) Initializing extension GLX
[ 2188.842] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 2188.842] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2188.842] (II) LoadModule: "evdev"
[ 2188.842] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2188.842] (II) Module evdev: vendor="X.Org Foundation"
[ 2188.842] compiled for 1.8.0, module version = 2.4.0
[ 2188.842] Module class: X.Org XInput Driver
[ 2188.842] ABI class: X.Org XInput driver, version 9.0
[ 2188.842] (**) Power Button: always reports core events
[ 2188.842] (**) Power Button: Device: "/dev/input/event2"
[ 2188.842] (II) Power Button: Found keys
[ 2188.842] (II) Power Button: Configuring as keyboard
[ 2188.842] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2188.842] (**) Option "xkb_rules" "evdev"
[ 2188.843] (**) Option "xkb_model" "evdev"
[ 2188.843] (**) Option "xkb_layout" "us"
[ 2188.883] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 2188.883] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2188.883] (**) Power Button: always reports core events
[ 2188.883] (**) Power Button: Device: "/dev/input/event1"
[ 2188.883] (II) Power Button: Found keys
[ 2188.883] (II) Power Button: Configuring as keyboard
[ 2188.883] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2188.883] (**) Option "xkb_rules" "evdev"
[ 2188.883] (**) Option "xkb_model" "evdev"
[ 2188.883] (**) Option "xkb_layout" "us"
[ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event3)
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event3"
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found 3 mouse buttons
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found relative axes
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2188.887] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
[ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
[ 2188.887] (II) No input driver/identifier specified (ignoring)
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.888] (**) Option "xkb_rules" "evdev"
[ 2188.888] (**) Option "xkb_model" "evdev"
[ 2188.888] (**) Option "xkb_layout" "us"
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.889] (**) Option "xkb_rules" "evdev"
[ 2188.889] (**) Option "xkb_model" "evdev"
[ 2188.889] (**) Option "xkb_layout" "us"
[ 2188.891] (II) config/udev: Adding input device PC Speaker (/dev/input/event0)
[ 2188.891] (II) No input driver/identifier specified (ignoring)
Xorg.0.log important (I think):
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.888] (**) Option "xkb_rules" "evdev"
[ 2188.888] (**) Option "xkb_model" "evdev"
[ 2188.888] (**) Option "xkb_layout" "us"
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.889] (**) Option "xkb_rules" "evdev"
[ 2188.889] (**) Option "xkb_model" "evdev"
[ 2188.889] (**) Option "xkb_layout" "us"
Why is he adding the keyboard 2 times, and why "xkb_layout" "us"? I need hr (croatian).
My first post Sorry, for the bad english.
Last edited by b3no (2010-07-22 23:45:29)

[ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
Add this
Section "ServerFlags"
Option "AllowEmptyInput" "no"
EndSection
EditL If the above didn't help, read this http://wiki.archlinux.org/index.php/Xor … d_settings
Last edited by karol (2010-07-22 12:06:04)

T430 keyboard layout impression

Today I've received first several T430 for our company, and they look generally not bad, but keyboard layout change naturally kills me. Can't even say how much I'm disappointed and irritated. For years Thinkpad keyboard layout which followed layout of big standard desktop keyboard probably most closely was one of its most loved features. First bad change was in T410 (or was it T400?) when they replaced Insert with big Delete button, so standard key combination Ctrl+Ins wouldn't work anymore if you try to hit Ins in it's usual place. And now just the end of the story - keyboard layout is like on any $500 worth Acer or Samsung.
It is not only changed - important features have gone. No more Back/Forward buttons, which were very usable at times. But when I noticed there is NO MORE NUMPAD, I realized this notebook is simply unusable for me, as I'm working with some programs which REQUIRE Numpad buttons. Not at least without normal external keyboard; and since I'm not going to drag it with me all the time, then it is unusable. Using Numpad buttons on notebook never was comfortable, but you have to pay for mobility and space. Ok, I will use my old good T61 as long as it is still alive, and then migrate to whatever, but not T430.
Oh yeah, and additinal thanks for hiding identification label with model and SN under the battery. Rapidly identifying booted notebook standing on a desktop just became more easy.

The move of standard keyboard layout of some standard key started with some manufactures like Toshiba at least five years ago when I got my HP Pavilion. I bought a 17" Toshiba but their placement of the right shift was replaced by an up arrow key which made typing nearly impossible. Constant correction of test was required. Ever since I paid attention to the ergonomics and rulled out dozens of notebooks in my son's and then my latest notebook.
The changes of typywriter keys from the normal position should never ever be allowed. You don't mess with the follow key placements - Enter Key, shift keys, space bar, and I would add the Cntrl, alt, Ins & Del keys to that. It seems the Del key is a migrant since it all over the place.
I had to find detailed photos of the T520 to verify the placement since the retailer don't sell them. Sticking to larger format or even 17" system does not guarantee the place is normal or as desired either. I have told sales people that a mutated little finger is required to reach the new shift key position. Its easier to keep those key where they should be than for me to get my little finger mutated by extending its length by at least a full digit in length.
Do the manufacturers think everyone is a two finger typer or something. I am not nor is anyone in our family. Erognomice is key and a first priority in the selection of a notebook, display quality is 2nd and ports 3rd. Then I can select whats under the hood.
I cannot leverage whats under the hood if the rest isn't there and I cannot use the system. Few small system conform to this anymore or have what it takes to endure the computing use of most business situations and even home use. Overheating is another issue and one reason I go for larger laptops, the keyboard and screen are larger giving me that benefit.
Buyer need to pay more attention and if it is not for them just move on to something that is designed properly. There is no excuse for a properly laid out keyboard nor a quality screen with TFT being at least 10 years old and panels have made huge advances. The only place for garbage is in the dump.
You'll have to change you systems standard and source something elsed. I don't believe mutating the fingers of the office users is an opton there either!!! LOL
T520 Model 4239 Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz
Intel Sandy Bridge & Nvidia NVS 4200M graphics Intel N 6300 Wi-Fi adapter
Windows 7 Home Prem - 64bit w/8GB DDR3

Keyboard layout keeps switching after 10.9.4 upgrade

After the recommended upgrade to Maverick 10.9.4, all of us in my group have the problem that the keyboard layout keeps switching every time a new Word document is opened (and possibly on a number of other occasions).
We have MacBookPros 2011, 2012, 2013, all regretting having upgraded to OsX 10.9.4. As per instructions, mine's a Retina late 2013 and got a 2.8 GhZ i7 with 8GB 1600MHz DDR3, 500GB SSD - no performance issues!
There have been two discussion threads as far as I can see; none with a solution.
"Fixing" the keyboard to a single one is not an option for polyglot people like us who actually need several keyboard layouts.
I have fed back to Apple as recommended weeks ago, but to no avail so far.
This persistent problem is driving all of us mad. Does no one on this list have any answers? Surely there's some setting somewhere that turned a perfectly well working system (10.9.3) into one that's costing us tens of minutes every single day (10.9.4)?
Thanks in advance,
Alexander

There is a box that no one had mentioned...
System Preferences---> Keyboard---> Input Source---> Uncheck the "Automatically switch to a document's input source. The input source is used until the document is closed."
kafetzou... You may want to delete the Turkish keyboard so that the English is on top of the list. Then re-add the Turkish keyboard, this will make it under the English. Though I don't know if this will help your problem, or the box that I mentioned above.
KOT

Thinkpad T530 Keyboard Layout

On the redesigned keyboard on the T530, the delete key is now where the PageUp key was on earlier ThinkPad models – viz: top right corner of keyboard and the PgUp & PgDn keys have been repositioned adjacent to the cursor movement keys. If your fingers are used to the previous Thinkpad keyboard layout, it is now very easy to unwittingly press the Delete key instead of the PgUp key, sometimes with unfortunate results.
The keyboard has a lovely feel but the new position of the Delete key to the top right and repositioning of other keys would seem to be a poorly thought out keyboard redesign affecting long time ThinkPad users that would be very used to the previous long standing layout.

the new keyboard is okay, but the layout is just wrong.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Windows 7, can't change default keyboard layout.

Hi!
It's not the first windows I install but its the first time I can't change the default keyboard layout. As usual I go in control pannel,region & language, (tab)keybard and languages, I press on change keyboard, Added the one I want ( Canadian french keyboard ) Put it on top of the list, tryed to delete the azerty keyboard I mistakly selected during the install and the option remove is greyed out. I tryed rebooting still the same issue. I also tryed to set it as default in the administrative tabs still no result.. Is there a regkey I can modify or something?
thanks!

G
o to: HKEY_CURRENT_USER\Keyboard Layout\Preload\1
Change the data in 1 to be 00001009
this should change your layout to the Canadian French one
The best way to do it!
Thank's!!

Losing extra keyboard layouts on reboot

Hi!
I use both the French-Canadian and US-Englsh keyboard layouts on my Mac and have for years.
Both are available in the Input Sources menu item and all usually works fine, except that when I reboot, I reboot with only the US Layout in that menu. The French-Canadian layout goes away and I have to re-enable it.
Funny thing is that in the Login screen, it is properly available.
I've deleted the ByHost Preferences tied to this pref (com.apple.HIToolbok.[insert long UUID Here].plist) as I found to do in a forum, but the problem persists.
Funny thing is that I have a similar issue with 1Password's Safari Extension keeps getting disabled and I have to launch that app as well when I reboot before it becomes available in Safari.
Anyone else having similar issues?
Someone I know had a similar problem and said it was tied to FileVault2, and that disabling it and reenabling it fixed it for him. I do not currently have FV2 active, although I have in the past.
I might just try to re-enable it to see...

Me again...
I thought it was solved but not. Loggin out and in works fine, but as soon as I reboot, I lose the extra keyboard layouts. I saw some other thread with a similar issue as well.
1Password has a similar issue where it won't load until I lanch the app itself, then reload Safari where the extension resides.
I'll see if this gets fixed in 10.8.1 when it comes out.
A bit of a hassltle to reenable the keyboard layout every time.
Maybe I'll lock the file to see...

Where are keyboard layout & input method files?

I was using the app "Monolingual" to free up hard drive space and accidentally deleted keyboard layout and input method files. Now I am unable to type or use keyboard commands in any application other than Safari. I have another Mac which I could copy the files from, but I do not know where those files are. I also have the original install discs from my MacBook Pro.
Any advice on how to get my keyboard back in working order?

Might be time for a relatively painless Archive & Install, which gives you a new/old OS, but can preserve all your files, pics, music, settings, etc., as long as you have plenty of free disk space and no Disk corruption, and is relatively quick & painless...
http://docs.info.apple.com/article.html?artnum=107120
Just be sure to select Preserve Users & Settings.
You can customize to eliminate things not needed.

Remove foreign language keyboard layout

How do i remove à keyboard layout?

Have you went to Settings>General>Keyboards>International Keyboards and tried to delete the unwanted keyboards? You only have the delete option if you have more than one keyboard.

Deleted my keyboard layouts

Similar Messages

Maybe you are looking for