Keyboard Layout, Bug? Bad Config?

Hey, love arch, love the support, love kittens.
after reading through the wiki and setting up arch i ran into a problem.
it seems my keyboard keeps reverting to the us layout.
here is my 10-keymap.fdi, it's placed in hal\policy.
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">gb</merge>
<merge key="input.xkb.variant" type="string" />
</match>
</device>
</deviceinfo>
i have tried both gb and uk. no luck.
when it didn't work i decided to specify it in my rc.conf.
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/London"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
that worked for a while, an hour or two, then changed. i am using kdemod. 4.xx,  my system is fully up to date.
Thanks.

got it working,
setxkbmap gb
curteous of your irc channel. thanks guys.

Similar Messages

  • DW CS5.5 Keyboard Layout BUG?! Help pls

    When I startup DW, and switch keyboard layout in CODE VIEW from eng to rus or from rus to eng all ok, window focus stay on CODE VIEW and I may write code perfectly, but after uses some any Snippet or simply open Snippet panel (SHIFT+F9) and then close .. I have big trouble, now when I switch keyboard layout I lose focus from CODE VIEW every time! and i must click left mouse button on code writing area to continue writing.. it very  not comfortable.
    U can try make this steps:
    1. Run DW
    2. press SHIFT + F9
    3. Try to write some CODE
    4. Now I press CTRL+SHIFT (keyboard switch) and lose MyFocus.. every time
    I think u understand my trouble, PLS tell what i can do to resolve this.
    sor for bad eng.

    Perhaps I'm not following your logic.  But why must you work with remote images?
    Let's say your products page is uploaded to https://yourDomain.com/
    and your local images are in an images folder that uploads to https://yourDomain.com/images/
    Given that workflow, everything will be on the secure server so there is no reason to use remotely hosted images during development.
    Nancy O.

  • Bug report: A keyboard layout is incorrect on the remote with Japanese keyboard

    This is a bug report for Microst Remote Desktop
    ===================================================
    ## Summary
    A keyboard layout is incorrect on the remote with Japanese keyboard
    ## Version Information, I tested
    * Client
        * Case 1
            * MacBook Pro with JIS106 Keyboard
            * Mac OS X Lion 10.7.5
            * Microsoft Remote Desktop 8.0.24308
        * Case 2
            * MacBook Pro with JIS106 Keyboard
            * Mac OS X Mavericks 10.9.1
            * Microsoft Remote Desktop 8.0.24308
    * Remote
        * Case 1
            * Windows 7 Professional Japanese
        * Case 2
            * Windows Server 2008R2 Datacenter Japanese
        * Case 3
            * Windows Server 2012R2 Datacenter Japanese
    ## Detail of bug
    When login from Mac OS X with Microsoft Remote Desktop, the keyboard layout is always incorrect on the remote.
    The client machine have a built-in keyboard of JIS 106 layout,
    and the primary language is set to Japanese.
    But on the remote, the keyboard layout is US 101.
    So a input of Shift+2 does not result " but @.
    I've seen the above behavior on the 3 remote enviornments described the above.
    This bug did not occcur with Microsoft Remote Desktop Connection Client for Mac 2.1.1, even if the system language is English and keyboard layout is Japanese.
    ## Captures
    I've took some of screen captures.
    I'm sorry for the capture includes Japanese words, so I added description in English.
    Capture 1:
    Mac OS X Keyboard Setting
    Capture 2:
    Windows Server 2012R2 Screen Keyboard
    Capture 3:
    Windows Server 2012R2 Screen Keyboard, with a additional registry key configured.

    This bug also affects the Canadian English settings.  If the client is set to Canadian English with a US keyboard the remote server is setup using a Canadian French keyboard.  Using the language selection in the toolbar you can temporarily correct
    the problem but the keyboard resets to french at the most inopportune times.  The was a problem in the earlier RDP client and was fixed so it's sad to see it reoccur in the new client.
    Lawrence

  • Bug report: A keyboard layout is incorrect on the remote with Hungarian and other "exotic" keyboard layouts

    This is a bug report for Microst Remote Desktop
    ===================================================
    ## Summary
    A keyboard layout is incorrect on the remote with Hungarian keyboard
    ## Version Information, I tested
    * Client
        * Case 1
            * MacBook Pro with HU101 Keyboard
    * Locale: Hungarian
            * Mac OS X Maverics 10.9.2
            * Microsoft Remote Desktop 8.0.6
    * Remote
        * Case 1
            * Windows Server 2003 R2 (English)
        * Case 2
            * Windows Server 2008 R2 (English)
        * Case 3
            * Windows 8.1 (Hungarian)
    ## Detail of bug
    When I connect to the listed remotes the client sets the keyboard layout to Latvian which is a completely different layout than Hungarian (not even close...).
    - On Windows 8 if I set the language on the login screen it stays on that language after the login.
    - On Windows Server 2003R2 and 2008R2 even if I set the language at login it will switch back to LV after the login.
    ## Attachments
    Unfortunately cannot include my shots because I'm not allowed to do this...
    ## End of report
    Please allow the users to set the correct "target" language on connection basis because the automatic method the app use to determine that is unreliable.

    Hi,
    Thanks for the feedback.
    I will forward this to the product team.
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Xorg bug: max number of possible keyboard layouts

    Dear forum,
    yesterday I installed Archlinux for the very first time on my home notebook.  It was the first time for me that I saw KDE 4 running, too.  After short time I encountered my first problem with that.
    It seems to be a bug in the Xorg protocol that limits the total of keyboard layouts to 4 (four).  This, however, used to be circumvented in KDE until version 3.5.10 to allow more layouts, but after they removed their hack (and with it the functionality) it's been reported several times as a bug.  The issue was even introduced to KDE4 as a feature by the kxkb maintainer so I don't expect any progress from this side soon.
    So KDE4 was rendered basically useless for me as I need at least 6 different layouts.  I came here to the forums for help because I don't know yet (after one day) what would be the "arch way" of eliminating this so-called feature without breaking my package dependencies.  Two possibilities came in my mind:
    1 Downgrade kxkb or whatever causes the problem to the last usable version.
    2 Downgrade KDE to the last usable version (that would be 3.5.10).
    Third possibility, as I'd like to use the machine for work, would be to install another distro that provides solution no 2.  I hesitate to do this because I picked arch for some reason and would like to become familiar with it.
    Any help would be much appreciated; thanks in advance!
    Philipp
    EDIT: I thought of a fourth solution that could be any other WM or DE that doesn't restrict itself to Xorg's limits.
    Last edited by parthenopaios (2009-06-30 16:08:51)

    Hi there,
    Well if you need high customizability, check out FVWM (I'm using that), *box or awesome. These three are really for powerusers and thus their configuration may be more difficult, but you can do more with them...
    In FVWM you can call any scripts you want via keystrokes (I believe in other mentioned WMs it is possible too). My Keboard Layout switching script is really lightwheight and it can store as many keyboard layouts as you want (at least it will cope with your 6 with no difficulties). It may work even in KDE, but you should then create a key binding.
    Search in this forum for xkbswitch. There was a discussion before about it.
    Ignas

  • Digital Cinema Desktop Preview, keyboard layout and other bugs - Leopard

    I just reinstalled my Mac Pro because I hoped it would fix some bugs... but no luck. Digital cinema desktop preview (dcdp) was working just fine until I installed the Aja Kona Lhe software, afterwards only dcdp for the main display was working, both dcdp and dcdp "full screen" have disappeared. The other things I was hoping 10.5.2 would fix are the problem FCP cannot remember the keyboard layout I use (azerty-belgium) - every time I start the program I have to choose the layout again - and the fact I cannot export using compressor straight from FCP using qmaster: Final cut pro generated an error! (this has never worked)
    If you are having the same problems as I do, maybe we should compare hardware to see what we have in common that could be causing this problem. As I have found during my searches, some computers have similar problems, others don't, sometimes it also matters if you've upgraded from Tiger of did a clean install, where upgrading it seems (yes really!!) gives the least problems...
    I really hope there will be a bugfix soon, because I'm sure I'm not the only one having these problems... or maybe I should just install Tiger and upgrade...???

    I vote for going back to Tiger. That is known to be stable. Leopard and FCP is unpredictable at the moment.
    Shane

  • [XFCE]Keyboard layout config sometimes gets reset after suspend/resume

    After I got suspend/resume working thanks to the help here, I have still another little problem with it: After suspend/resume the keyboard layout configuration in the corresponding xfce-panel plugin is sometimes reset to US. The keyboard layout should be Russian/German with switching the layouts with LCtrl+LShift. In the xorg.conf everything is fine, but it seems to be disregarded:
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "de,ru"
    Option "XkbVariant" ",winkeys"
    Option "XkbOptions" "grp:ctrl_shift_toggle"
    EndSection
    The settings that I make in the panel-applet via its configuration dialogue work though, but they sometimes get reset after a suspend/resume.
    The XFCE session is started via following command in ~/.xinitrc:
    exec ck-launch-session dbus-launch xfce4-session
    Thanks for any hint,
    PhotonX

    I see. Then you should maybe add debug output to check whether the script is run at all and if yes, where it fails. Like
    button/lid)
    echo "lid action caught" >> /home/lid.log
    case "$3" in
    close)
    logger 'LID closed'
    # Suspend and lock the screen
    /usr/sbin/pm-suspend &
    DISPLAY=:0.0 su -c - miki /usr/bin/slimlock
    echo "lid closed" >> /home/lid.log
    open)
    logger 'LID opened'
    # Set the keyboard layout again on IT
    setxkbmap it
    echo "lid opened" >> /home/lid.log
    logger "ACPI action undefined: $3"
    echo "something wrong happened" >> /home/lid.log
    esac
    and then check /home/lid.log after lid close&open.

  • [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)

  • Screen locked with non-English keyboard layout selected

    Hello,
    I use two keyboard character sets for keyboard. The switch between them is Command-Space.
    I also have password requirement for waking up or going from screen saver.
    Now if screensaver starts with non-English layout selected, I'm not able to login:
    password is not accepted because keyboard layout is not English and switching
    to English layout does not work in unlocking window.
    Is there any way to change layout while in the unlock window?
    Thanks

    Yes you are right, this is not a bug, it's just bad user interface. Just imagine the following scenario...
    Writing a paper, switching to Greek to enter a couple of characters and leaving the mac idle for 5 mins.
    The lock screen comes up asking for a password, unfortunately the user didn't change the language
    before the mac was left idle and there is no option to change the language in the lock screen.
    User has to hard reset to access the mac and let's hope that the user was saving his paper frequenlty.
    So from a coding point of view this is not a bug, but from a user interface design it is a huge flaw

  • [Solved] Can't login with current keyboard layout and `@` in password

    Hi, I'm a new arch user. I followed archwiki to install Enlightenment17. All went fine but I have a problem to login since during setup I inserted '@' in root/regular user passwords. During setup I selected the Italian layout and all seems ok, except grafical login through entrance (from aur, but I tested also kdm, with same results): password not recognized. Before asking, is not a CAPS/NUMLOCK issue since the password works using it in console login. I discovered that I can type '@' with the following combination: SHIFT+2; in an italian keybord this should print a double quote (") but in entrance (and kdm) it correponds to '@'. After login this way, the keyboard works normally (for instance using 'su'). So the problem is limited to graphical login (entrance and kdm) during which a different keyboard layout is used.
    Did I miss some config file?
    For the sake of clarity:
    1) /etc/locale.gen has "it_IT.UTF-8 UTF-8" uncommented
    2) /etc/locale.conf contains "LANG=it_IT.UTF-8"
    3) /etc/vconsole.conf contains "KEYMAP=it"
    4)
    $ locale
    LANG=it_IT.UTF-8
    LC_CTYPE="it_IT.UTF-8"
    LC_NUMERIC="it_IT.UTF-8"
    LC_TIME="it_IT.UTF-8"
    LC_COLLATE="it_IT.UTF-8"
    LC_MONETARY="it_IT.UTF-8"
    LC_MESSAGES="it_IT.UTF-8"
    LC_PAPER="it_IT.UTF-8"
    LC_NAME="it_IT.UTF-8"
    LC_ADDRESS="it_IT.UTF-8"
    LC_TELEPHONE="it_IT.UTF-8"
    LC_MEASUREMENT="it_IT.UTF-8"
    LC_IDENTIFICATION="it_IT.UTF-8"
    LC_ALL=
    Thanks for any help.
    Last edited by bull3t (2013-03-03 14:10:15)

    cfr wrote:Have you tried specifying a variant?
    I exclude a variant problem considering that in any other condition the keyboard layout is right. The system is configured for an it KEYMAP but it is obvious that in entrance/kdm is used an 'us' map. Is this hardcoded somewhere? I also tryed to comment out any entry in /etc/locale.gen except 'it_IT.UTF-8 UTF-8': still 'us' keymap in graphical login screen.
    Probably a kind user with a non-us keyborad layout could create a dummy user with password containing '@' or '#' or any other special symbol to verify that this condition is reproducible, a first step for a bug report.
    Cheers

  • Can't set keyboard layout in X

    Hello!
    Some days ago X stopped setting XkbLayout to "no" despite me having specified it in /etc/X11/xorg.conf.d/01-keyboard-layout.conf.
    The layout is different when setting it with setxkbmap, e.g. special AltGR characters like ] is gone.
    I use .conf files in /etc/X11/xorg.conf.d/ and synaptics touchpad apparently works.
    rasmus@angrist ~ % cat /etc/X11/xorg.conf.d/01-keyboard-layout.conf
    Section "InputClass"
    Identifier "Keyboard Defaults"
    MatchIsKeyboard "yes"
    Option "XkbLayout" "no"
    Option "XkbVariant" "nodeadkeys"
    Option "XkbOptions" "compose:ralt, caps:escape, terminate:ctrl_alt_bksp"
    EndSection
    rasmus@angrist ~ % cat /etc/X11/xorg.conf.d/10-evdev.conf
    # Catch-all evdev loader for udev-based systems
    # We don't simply match on any device since that also adds accelerometers
    # and other devices that we don't really want to use. The list below
    # matches everything but joysticks.
    Section "InputClass"
    Identifier "evdev pointer catchall"
    MatchIsPointer "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    EndSection
    Section "InputClass"
    Identifier "evdev keyboard catchall"
    MatchIsKeyboard "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "Xkblayout" "no"
    EndSection
    Let me supply some output. The output of `setxkbmap -print -verbose 10' before running `setxkbmap no':
    Setting verbose level to 10
    locale is C
    Trying to load rules file ./rules/evdev...
    Trying to load rules file /usr/share/X11/xkb/rules/evdev...
    Success.
    Applied rules from evdev:
    rules: evdev
    model: evdev
    layout: us
    options: compose:ralt, caps:escape, terminate:ctrl_alt_bksp
    Trying to build keymap using the following components:
    keycodes: evdev+aliases(qwerty)
    types: complete
    compat: complete
    symbols: pc+us+inet(evdev)+capslock(escape)+compose(ralt)+terminate(ctrl_alt_bksp)
    geometry: pc(pc104)
    xkb_keymap {
    xkb_keycodes { include "evdev+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compat { include "complete" };
    xkb_symbols { include "pc+us+inet(evdev)+capslock(escape)+compose(ralt)+terminate(ctrl_alt_bksp)" };
    xkb_geometry { include "pc(pc104)" };
    After running `setxkbmap no':
    Setting verbose level to 10
    locale is C
    Trying to load rules file ./rules/evdev...
    Trying to load rules file /usr/share/X11/xkb/rules/evdev...
    Success.
    Applied rules from evdev:
    rules: evdev
    model: evdev
    layout: no
    options: compose:ralt, caps:escape, terminate:ctrl_alt_bksp
    Trying to build keymap using the following components:
    keycodes: evdev+aliases(qwerty)
    types: complete
    compat: complete
    symbols: pc+no+inet(evdev)+capslock(escape)+compose(ralt)+terminate(ctrl_alt_bksp)
    geometry: pc(pc104)
    xkb_keymap {
    xkb_keycodes { include "evdev+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compat { include "complete" };
    xkb_symbols { include "pc+no+inet(evdev)+capslock(escape)+compose(ralt)+terminate(ctrl_alt_bksp)" };
    xkb_geometry { include "pc(pc104)" };

    Hey!
    I got some success with disabling iBus in .xinitrc:
    #### iBUS eviroment variables
    #export XIM="ibus"
    #export GTK_IM_MODULE="ibus"
    ##export QT_IM_MODULE="xim"
    #export QT_IM_MODULE="ibus"
    #export XMODIFIERS="@im=ibus"
    #ibus-daemon -d -x &
    as well as having this config in /etc/X11/xorg.conf.d/01-keyboard-layout.conf:
    Section "InputClass"
    Identifier "Keyboard Defaults"
    MatchIsKeyboard "yes"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "no"
    Option "XkbVariant" "nodeadkeys"
    # Option "XkbOptions" "compose:ralt, caps:escape, terminate:ctrl_alt_bksp"
    EndSection
    DIsabling iBus solved autoconfig of keyboard to "no", and the new config with the addition of XkbModel solved not being able to use AltGr. I recon there is some bug in iBus and the config for X has changed in some way. Also, writing ^ and ~ and other characters in URxvt works now, as it has not worked for a long time, probably some years. I always thought there had something to do with Awesome.

  • Not work 3 keyboard layouts

    Then I use 2 languages,  Option          "XkbLayout"     "us,lt" in /etc/X11/xorg.conf, then work keyboard layout.
    If I use 3 languages in XkbLayout, then not work layout.
    There some part of /etc/X11/xorg.conf:
    Section "InputDevice"
            Identifier      "Generic Keyboard"
            Driver          "kbd"
            Option          "CoreKeyboard"
            Option          "XkbRules"      "xorg"
            Option          "XkbModel"      "pc105"
            Option          "XkbLayout"     "us,lt,ru"
            Option          "XkbOptions"    "grp:alt_shift_toggle"
    EndSection

    You didn't tell what's your problem is though. I suppose you just cannot switch layouts with Alt-Shift, right?
    Try if Shift-Alt (sic!) works for you. Also try grp:ctrl_shift_toggle (only RightCtrl-Right shift work, LeftCtrl-LeftShift switches to first layout instantly).
    alikas wrote:So it is bug?
    Yes. Both xkeyboard-config 0.6 and 0.9 are buggy, but bugs are triggered for specific keyboard layout combinations.
    For example, I had bug with 0.6 with my xorg config, while many others don't.
    0.9 fixed bug for me, but now other people have problems.
    As you may see in that bug report the problem mostly depends on XkbLayout combination, though I thought it was due to grp:alt_shift_toggle first.

  • How to Make a Keyboard Layout for X11/OpenOffice

    While OpenOffice has a setting to use standard OS X keyboard layouts, you may find that some of these do not work correctly, especially if deadkeys are involved. In that case you will need to create a new layout in the form of a keymap file, which you place in your home folder and invoke when needed via the command "xmodmap mykeymap" in an xterm (or by putting the same line in some config file).
    You keymap file should just contain the minimum necessary modifications of the default X11 map, which you can see by doing the command "xmodmap -pke | less" in an xterm (after making sure the preference item for using OS X layouts is turned off).
    Some fiddling with the entries of your file may be necessary, as both X11 and apps that use it have quirks and bugs of various sorts. Below is the file I made to do Vietnamese in OpenOffice as an example:
    keycode 26 = abreve
    keycode 27 = 0x00E2
    keycode 28 = 0x00EA
    keycode 29 = 0x00F4
    keycode 30 = dead_hook
    keycode 31 = dead_grave
    keycode 33 = dead_belowdot
    keycode 34 = dead_tilde
    keycode 36 = dead_acute
    keycode 37 = U0111
    keycode 38 = U01A1
    keycode 41 = U01B0

    This is a feature Apple should definitely add customization to on OS X.
    You can make custom keyboard layouts that include any characters you want using Ukelele.
    http://scripts.sil.org/cms/scripts/page.php?siteid=nrsi&itemid=ukelele
    I doubt Apple is going to incorporate this into OS X, but you can suggest it here:
    http://www.apple.com/feedback/macosx.html

  • [CLOSED] Unable to set keyboard layout from /etc/X11/xorg.conf.d/

    This is my /etc/X11/xorg.conf.d/10-keyboard.conf:
    Section "InputClass"
    Identifier "keyboard-layout"
    MatchIsKeyboard "on"
    Option "XkbLayout" "cz,us"
    Option "XkbOptions" "grp:alt_shift_toggle"
    EndSection
    I wrote the according to the wiki recommendations, but it doesn't work. Issuing setxkbmap -layout "cz,us" -option "grp:alt_shift_toggle" automatically after logging in serves as a temporary solution, but I'm highly interested in fixing the primary issue. I would greatly appreciate if someone helped my find the error in my config file and/or posted their way to change the xorg keyboard layout in order to compare it with my way and find the error. Also note that I'm using Awesome WM so desktop environment ways of setting the keyboard layout aren't applicable in my case.
    Last edited by C5OK5Y (2012-12-28 15:01:25)

    @chris_l: Thank you for your /etc/X11/xorg.conf.d/01-keyboard-layout.conf.
    I have found out that the actual problem isn't in the configuration file but in the actual keyboard (more accurately xorg) - the keyboard gets incorrectly identified and xorg seems to think that it's a pointer (mouse). When I connect a different keyboard, the layout gets set correctly, xorg just isn't setting the keyboard layout correctly to the keyboard that I use. I have filed a bug report so this thread can be considered closed.
    Last edited by C5OK5Y (2012-12-29 12:58:44)

  • New keyboard layout appeared after update - how to remove it?

    Hello community,
    I'm using two keyboard layouts RU and DE and switching them with Ctrl+Shift. After a recent update a third keyboard layout appeared - US. I checked /etc/X11/xorg.conf, /etc/hal/fdi/policy/10-keymap.fdi and /etc/rc.conf but in all of them there is no US layout. Setting everything there up for the DE and RU layout didn't help, still the US layout is in the layouts list in Gnome. If I remove it from that list, it appears after the next reboot. So how can I go rid of it?
    Here are the config files:
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "de,ru"
    Option "XkbVariant" ",winkeys"
    Option "XkbOptions" "grp:alt_shift_toggle"
    EndSection
    <?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
    <deviceinfo version="0.2">
    <device>
    <match key="info.capabilities" contains="input.keymap">
    <append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
    </match>
    <match key="info.capabilities" contains="input.keys">
    <merge key="input.xkb.rules" type="string">base</merge>
    <!-- If we're using Linux, we use evdev by default (falling back to
    keyboard otherwise). -->
    <merge key="input.xkb.model" type="string">keyboard</merge>
    <match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
    string="Linux">
    <merge key="input.xkb.model" type="string">evdev</merge>
    </match>
    <merge key="input.xkb.layout" type="string">de,ru</merge>
    <merge key="input.xkb.variant" type="string">nodeadkeys,winkeys</merge>
    <merge key="input.xkb.options" type="string">grp: ctrl_shift_toggle</merge>
    </match>
    </device>
    </deviceinfo>
    # /etc/rc.conf - Main Configuration for Arch Linux
    LOCALE="de_DE.utf8"
    HARDWARECLOCK="local"
    USEDIRECTISA="no"
    TIMEZONE="Europe/Berlin"
    KEYMAP="de-latin1-nodeadkeys"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    Thanks, PhotonX

    Thanks for your input, guys, I think, this issue has been already reported (quite a long time ago) which is even the top entry of the most wanted tasks: http://bugs.archlinux.org/toplevel/proj1 So the only thing we can do is to follow the comments and to hope for a fix.

Maybe you are looking for