[Solved] Keyboard layout - best practice

I have two laptops running Arch Linux. On the first I have set norwegian keyboard with:
Option "XkbLayout" "no"
in then keyboard section of /etc/X11/xorg.conf.d/10-evdev.conf.
On the second I have usede
localectl set-x11-keymap no
from CLI to set the keymap.
What ist best practice?
Last edited by torors (2014-07-30 14:53:22)

localectl creates /etc/X11/xorg.conf.d/00-keyboard.conf
$ cat /etc/X11/xorg.conf.d/00-keyboard.conf
# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "pl"
EndSection
Another computer:
$ cat /etc/X11/xorg.conf.d/00-keyboard.conf
# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "pl"
Option "XkbModel" "pc105"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
Neither of hem has /etc/X11/xorg.conf.d/10-evdev.conf, but they have /usr/share/X11/xorg.conf.d/10-evdev.conf - xorg-server 1.16 style.
Last edited by karol (2014-07-30 12:54:24)

Similar Messages

Layout Best Practices

<b>Problem Description</b>
A developer needs to be able to create a rich client interface and avoid basic layout issues that tend to be pervasive across screens and applications. There are a number of low-level layout issues within ADFv that:
<ol>
<li>Tend to repeat themselves across screens and across applications.</li>
<li>Impact perception of usability, quality, and fit ‘n’ finish.</li>
<li>Are annoying to users in the aggregate. Although no single item is terrible, but a collection of 6 items, repeating themselves on multiple screens gets frustrating and detracts from the message.</li>
</ol>
In most cases, there’s a simple approach and best practice that will assist developers in avoiding these pitfalls.
<b>Technical Best Practice Description</b>
This Layout Best Practices document provides a list of known layout issues that are encountered when developing a Rich Client Interface and how to avoid them in your application development.
Various ADF Components are described and demonstrated in this document including document, showDetailItem, decorativeBox, panelSplitter, panelStretchLayout, panelBorderLayout, and so on. It takes many of these components in combination to achieve the desired layout for a page and / or an application.
Click here to see the document that describes these best practices.
Edited by: Richard Wright on Nov 17, 2009 5:26 PM

Hi,
Try this link: [Layout Best Practices|http://www.oracle.com/technology/products/adf/patterns/11/layoutBestPractices.html]
Regards,
Edited by: Richard Wright on Nov 17, 2009 5:27 PM

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

[SOLVED] keyboard layout no longer exists?

Hi there,
I noticed my keyboard layout switched back from azerty to qwerty. Also, latest upgrade shows my keyboard layout can't be opened
upgrading linux [##################################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.8.3-2-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
==> WARNING: Hook 'pata' is deprecated. Replace it with 'block' in your config
-> Running build hook: [block]
-> Running build hook: [keymap]
cannot open file fr_latin9
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
I suppose this is related. Has fr_latin9 been removed?
Last edited by brazzmonkey (2013-03-20 08:44:33)

I don't see it in /usr/share/kbd/consolefonts, so I guess that means yes. Maybe you can see if you can pull an old kbd package from the Arch Rollback Machine and stick the layout in there (and maybe the font too... not sure how that works).

[SOLVED]xpra + winswitch - best practice due to /etc/X11/xorg.conf.d/*

Running xpra causes some headaches.
The application builds fine and installs just perfectly, the troubles comes from the default Xorg configuration is no longer stored in /etc/X11/xorg.conf, it's now stored and read from numerous files under /etc/X11/xorg.conf.d/ where just so happen to be my 5-nvidia.conf.
Starting xpra via:
xpra start :100
Causes:
X.Org X Server 1.14.3
Release Date: 2013-09-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.11.0-1-ARCH x86_64
Current Operating System: Linux archie 3.11.2-1-ARCH #1 SMP PREEMPT Fri Sep 27 07:35:36 CEST 2013 x86_64
Kernel command line: root=/dev/sda1 rw initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
Build Date: 13 September 2013 01:28:59PM
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/home/torxed/.xpra/Xorg.:100.log", Time: Thu Oct 3 19:56:30 2013
(++) Using config file: "/etc/xpra/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
setversion 1.4 failed
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(EE)
Fatal server error:
(EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/home/torxed/.xpra/Xorg.:100.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
2013-10-03 19:56:30,893
2013-10-03 19:56:30,893 Xvfb command has terminated! xpra cannot continue
2013-10-03 19:56:30,894
2013-10-03 19:56:30,895 removing socket /home/torxed/.xpra/archie-100
tl;dr: 5-nvidia.conf is trying to get loaded after xf86-video-dummy is loaded (which is the default for xpra).
Now to the question: What's the best practice because there's no information about this issue, and i can't be the only one who's run in to this since the xorg.conf was removed. At the moment I move all my nvidia configs out of the way, start xpra and move them back in. This works for the better part as long as i execute xpra with my own scripts.
But is there a better way (which doesn't perhaps include recreating xorg.conf since that appears to be something you should walk away from)?
Last edited by Torxed (2013-10-04 10:29:35)

Good thinking! (xpra is basically just screen but for x, or a X11 tunnel via SSH).
After a really quick poking around and remembering that xpra really just uses xorg-server-xvfb and at the very bottom of /etc/xpra/xpra.conf there's a line that says:
xvfb=xpra_Xdummy -dpi 96 -noreset -nolisten tcp +extension GLX +extension RANDR +extension RENDER -logfile ${HOME}/.xpra/Xorg.${DISPLAY}.log -config /etc/xpra/xorg.conf
Appending -configdir appears to be working.
Here are the full steps:
[torxed@archie ~]$ sudo cp -r /etc/X11/xorg.conf.d /etc/xpra/
[torxed@archie ~]$ sudo rm /etc/xpra/xorg.conf.d/*nvidia*
[torxed@archie ~]$ sudo sed -i '$s/$/ -configdir \/etc\/xpra\/xpra.conf.d/' /etc/xpra/xpra.conf
*nvidia* would have to match your graphic-driver-config that would cause xorg-server-xvbf to crash.
I'll update the wiki and put a mention on the package about it because this either has to be standard or well known from the start because it really just breaks the package all together.
Last edited by Torxed (2013-10-04 10:29:09)

[SOLVED] Keyboard layout not setting correctly after gnome 3.14 update

Hey all,
After the gnome 3.14 update my keyboard appears to be reverting to US when I want to have it set to UK layout. It was fine before the update, and I have i3 & XFCE installed and for both of those my keyboard layout is getting set to UK just fine, so it appears to be just the gnome 3.14 update that is the problem.
Here is my contents of /etc/X11/xorg.conf.d/10-keyboard.conf:
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "gb"
EndSection
Anyone have any ideas what the problem could be?
Last edited by Morgy (2014-10-18 17:18:09)

My situation showed an extra issue related to this change.
After the upgrade I started getting two layouts (us,us) instead of just one (us).
$ setxkbmap -query
rules: evdev
model: pc104
layout: us,us
variant: ,
options: ctrl:nocaps
That broke my variant setting, which was altgr-intl (set via /etc/X11/xorg.conf.d/10-evdev.conf). I was able to manually set that to "altgr-intl,altgr-intl" (with setxkbmap), and that worked.
After adding an input source as described above, of "English (international AltGr dead keys)", everything started working again for my purposes, without manually running setxkbmap, but I still have the extra layout:
$ setxkbmap -query
rules: evdev
model: pc104
layout: us,us
variant: altgr-intl,
options: ctrl:nocaps
Does anyone know a current method for completely disabling GNOME's keyboard management?
(I've tried several things from Google, but nothing seems to work for the current version).

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

[SOLVED]Keyboard layout changed.

Hi i did a major upgrade yesterday, having waited to do an upgrade for a few weeks because of wonky nvidia drivers i finally managed to Syu yesterday and upgraded 133 packages. Everything works fine it seems apart from one thing i noticed this morning, my keyboard layout has changed from the english GB one. any suggestions how i can change it?
here's the relative part of my rc.conf -
LOCALE="en_GB.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/London"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
not sure where else to look for changes. i run openbox desktop btw
Last edited by yabasta (2010-07-28 11:56:34)

Thanks for the help loafer i'd changed /etc/X11/xorg.conf like so -
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "gb"
EndSection
but that didn't work. so i followed the archwiki link http://wiki.archlinux.org/index.php/Xorg#InputClasses from the news article you pasted. Seemed i needed to make a keyboard.conf file in /etc/X11/xorg.conf.d, which i did -
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "gb"
EndSection
A quick logout and login and now i have my gb layout. Sadly my keyboard model isn't in /usr/share/X11/xkb/rules/base.lst so i can't set
"Xkbmodel" and get all the functions from my keyboard. never mind. thanks again for the help loafer
@Mr.Elendig
yes, i thought as much. but i'm still a newb and was just trying to give some info, seems it was a futile gesture.
Last edited by yabasta (2010-07-28 11:55:48)

[SOLVED] Keyboard layout switching

Hello,
I have a problem with keyboard layout switching key.
Just notice it not working anymore...
here is my key setting in xorg.conf
Section "InputDevice"
Identifier "Keyboard"
Driver "kbd"
Option "XkbLayout" "us,th"
Option "XkbOptions" "grp:alt_shift_toggle"
EndSectionp
Last edited by xcession (2008-11-05 13:23:57)

bender02 wrote:
xcession wrote:EndSectionp
extra p?
Seriously though, it looks fine to me. There's a wiki article http://wiki.archlinux.org/index.php/Con … youts_in_X
I'd try adding
Option "XkbRules" "xorg"
although that could be automatic.
Oops! it's my typo when posting that post...
Added Option "XkbRules" "xorg"
but still doesn't work...:(

[SOLVED]Keyboard layout messy after wake up or using KVM-switch

After waking up the computer from suspension or using my KVM-switch, the keyboard layout is pretty messed up.
"qwertzuiopü+" becomes ".,ñpyfgchl"
"asdfghjklöä#" becomes "aoeuidrtnsḉ"
"<yxcvbnm,.-" becomes "<-qjkxbmwvz"
I know the origin of the problem is that XKB is only set by my .xinitrc. But how can I bypass this? How can I set XKB with the German layout by default?
Last edited by Dun (2015-01-21 13:41:50)

alphaniner wrote:
Try a conf file in /etc/X11/xorg.conf.d. Here's mine:
$ cat /etc/X11/xorg.conf.d/00-keyboard.conf
# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
Identifier "system-keyboard"
Driver "evdev"
Option "XkbLayout" "carpalx"
Option "XkbOptions" "ctrl:swapcaps"
EndSection
Ah thank you very much!

[Solved] keyboard layout not being picked up

So I recently ran into a problem where my keyboard layout is not being correctly set up. When I run
[ben@ksack ~]$ setxkbmap -print -verbose
I am greeted with
Couldn't interpret _XKB_RULES_NAMES property
Use defaults: rules - 'base' model - 'pc105' layout - 'us'
Trying to build keymap using the following components:
keycodes: xfree86+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+inet(pc105)
geometry: pc(pc105)
xkb_keymap {
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(pc105)" };
xkb_geometry { include "pc(pc105)" };
My config in /etc/X11/xorg.conf.d/10-evdev.conf is the following
# 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" "gb"
EndSection
Section "InputClass"
Identifier "evdev touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev tablet catchall"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
If I run
setxkbmap -layout gb
that fixes the problem but I can't figure out
Why my config stopped working
Where to include setxkbmap such that I get my map loaded correctly
Any and all help greatly appreciated.
Last edited by benjumanji (2012-06-15 23:00:58)

ahhh. My locale is certainly wrong. I shall fix that, but that shouldn't effect the way that X configures the keyboard, right? I changed it anyway. Problem remains. I also fixed up my .xinitrc, that didn't help either. I think there must be something deeply wrong somewhere.
What I mean by worked and then didn't is that at my keyboard was fine (gb) with X, then at some point after an upgrade it ceased to work properly i.e. was being configured as US kb.

[SOLVED] Keyboard layout changed to English after xorg update

Hello all,
I just logged in to my Arch box after a few days of not using it, and issued
pacman -Syu
and upgraded, among others, xorg-server and xorg-server-common to versions 1.11.1-2. Now, after logging out and back in to restart X, I find that my keyboard layout is now (presumably American) English. However, looking under Menu -> Settings -> Keyboard in the XFCE menu, I still see the preferred layout set to Norwegian, as I want. Messing with the settings in this GUI seems to have no effect. However,
setxkbmap no
still works. Anybody experience something similar or have any hints?
Here's the output of
sudo less /var/log/pacman.log | grep 2011-10-12
[2011-10-12 21:05] Running 'pacman -Syu'
[2011-10-12 21:05] synchronizing package lists
[2011-10-12 21:05] starting full system upgrade
[2011-10-12 21:07] update desktop mime database...
[2011-10-12 21:07] removed comix (4.0.4-5)
[2011-10-12 21:07] installed python2-distribute (0.6.21-1)
[2011-10-12 21:07] update desktop mime database...
[2011-10-12 21:07] installed mcomix (0.94-2)
[2011-10-12 21:07] upgraded gtksourceview3 (3.2.0-1 -> 3.2.1-1)
[2011-10-12 21:07] upgraded imagemagick (6.7.2.8-1 -> 6.7.3.0-1)
[2011-10-12 21:07] upgraded libass (0.9.13-1 -> 0.10.0-1)
[2011-10-12 21:07] upgraded libsasl (2.1.23-7 -> 2.1.23-8)
[2011-10-12 21:07] upgraded lsof (4.84-3 -> 4.85-1)
[2011-10-12 21:07] upgraded mkinitcpio (0.7.2-1 -> 0.7.3-1)
[2011-10-12 21:07] upgraded mpfr (3.1.0-2 -> 3.1.0.p1-1)
[2011-10-12 21:07] upgraded python2-pytz (2011h-1 -> 2011k-1)
[2011-10-12 21:07] upgraded shared-mime-info (0.90-1 -> 0.91-1)
[2011-10-12 21:07] upgraded transmission-gtk (2.33-1 -> 2.41-2)
[2011-10-12 21:07] upgraded wine (1.3.29-2 -> 1.3.30-1)
[2011-10-12 21:07] upgraded xf86-input-evdev (2.6.0-3 -> 2.6.0-4)
[2011-10-12 21:07] upgraded xf86-video-nouveau (0.0.16_git20110726-1 -> 0.0.16_git20110829-1)
[2011-10-12 21:07] upgraded xkeyboard-config (2.2.1-1 -> 2.4.1-1)
[2011-10-12 21:07] upgraded xorg-server-common (1.10.4-1 -> 1.11.1-2)
[2011-10-12 21:07] upgraded xorg-server (1.10.4-1 -> 1.11.1-2)
[2011-10-12 21:07] upgraded xorg-xinit (1.3.0-3 -> 1.3.1-1)
[2011-10-12 21:07] Running 'pacman -S alsa-plugins lib32-alsa-plugins'
[2011-10-12 21:07] installed alsa-plugins (1.0.24-2)
[2011-10-12 21:07] installed lib32-alsa-plugins (1.0.24-1)
[2011-10-12 21:09] Running 'pacman -Rs libcanberra lib32-libxxf86dga'
[2011-10-12 21:09] removed lib32-libxxf86dga (1.1.2-1)
[2011-10-12 21:09] removed libcanberra (0.28-2)
And of
sudo less /var/log/Xorg.0.log | grep key
[ 679.213] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 679.213] (--) Power Button: Found keys
[ 679.213] (II) Power Button: Configuring as keyboard
[ 679.242] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 679.242] (--) Power Button: Found keys
[ 679.242] (II) Power Button: Configuring as keyboard
[ 679.242] (**) LITEON Technology USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 679.242] (--) LITEON Technology USB Multimedia Keyboard: Found keys
[ 679.242] (II) LITEON Technology USB Multimedia Keyboard: Configuring as keyboard
Thank you for any help!
Last edited by mariusmeyer (2011-10-12 21:52:19)

It seems to be treated as standard behavior here (I had the same problem though):
https://wiki.archlinux.org/index.php/Beginners'_Guide#Non-US_keyboard
https://wiki.archlinux.org/index.php/GN … ard_layout
Last edited by viking60 (2011-10-12 20:47:37)

[SOLVED] Keyboard layout in xorg 1.9

I'm trying to add a Romanian layout and I don't know how.
Most of the topics I've seen are OLD. They may or may not've worked with previous xorg versions, I don't know. They certainly didn't for me.
Please help.
Here's my xorg.conf:
# Section "ServerFlags"
# Option "ignoreABI" "True"
# EndSection
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "gb,ro"
Option "XkbOptions" "grp:caps_toggle,grp_led:scroll"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30.0 - 110.0
VertRefresh 50.0 - 150.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nouveau"
VendorName "nVidia Geforce 7025"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "DynamicTwinView" "false"
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
Adding this didn't help:
Option "XkbLayout" "gb,ro"
Option "XkbOptions" "grp:caps_toggle,grp_led:scroll"
Last edited by DSpider (2012-02-17 08:37:46)

The kind people from the IRC channel suggested I add this bit at the very end of the "/etc/X11/xorg.conf" file (instead of "/etc/X11/xorg.conf.d/10-evdev.conf" - tho it would've probably worked that way too):
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "us, ro"
Option "XkbVariant" "std"
Option "XkbOptions" "grp:caps_toggle, grp_led:scroll"
EndSection
Apparently it works. I just have to hold AltGr and press s, q , a, i, t, etc to type ș â ă î ț etc. But how do I set it to ; { } ] ' ", etc, like the default behaviour in Windows... ? I would like them to correspond to this layout.
Because this is not the "standard" ("std") version...
I may have to edit the "/usr/share/X11/xkb/symbols/ro" file to map them.
Unless there's a better way ?
Last edited by DSpider (2010-12-11 13:19:16)

[Solved] keyboard layout

I think i've set the keyboard properly but I clearly haven't after a rebook the alter for number 2 is different and the ash key. I believe it has returned to it's defaul but am not sure why?
localectl status
Says that the key layout is N/A I believe this is wrong but am not sure what I should change?
Sorry for the noob question I am new.
Any advice welcome thanks
Last edited by Arch-Hoochie (2014-09-23 18:15:35)

https://wiki.archlinux.org/index.php/Be … and_keymap
Not an Installation issue, moving to NC...

Crystal Report layout, best practice

SAP B1 8.81
I'm having only spotty success with CR layouts and I've experimented quite a bit. What I'd like to do is extensively modify 1 system Crystal Report and then bring it in as a layout, and apply it to AR Item Quote, Order, DN, Invoice, and Return. Does it matter which system document I start with? After I've got a master layout that works for all, what if I need to add small tweaks to a particular document, say a special field that appears in Invoice headers only? How do I do that? These questions aren't addressed in the 'How to Work with CR in SBO' guide.
Anybody have some global guidelines they'd like to offer that lead to success?

Hi Cindy
We have done what you want to do in 8.8 a number of times. It also works in 8.81 but we have been having similar login issues that other users have reported.
You use the ObjectId@ parameter to determine the type of object being printed and use that to suppress fields, sections etc.
Where there are specific formats required for different object types you can define multiple sections, (eg page headers, group headers, detail lines etc) and show or suppress based on the object type as required.
This can lead to very messy and complicated reports if there are a lot of differences and so you will need to make a decision as to the tradeoffs between having one huge report which is hard to maintain or a couple of simpler ones.
Given the load time issues, which seem to be related to the number of subreports etc you might also find some benefit in, for example, having a separate master layout for the documents that dont need to show batches and serial numbers and some of the final details such as downpayments and another layout for documents that need to show everything. Once again, you need to trade off here.
We have generally started with the invoice layout as our master since that has everything in it.
Hope this helps
Rob

[Solved] Keyboard layout - best practice

Similar Messages

Maybe you are looking for