Xorg (Français)
From ArchWiki
i18n |
---|
Dansk |
English |
Ελληνικά |
Español |
Polski |
Русский |
Česky |
Italiano |
简体中文 |
Türkçe |
Français |
Introduction
Xorg est l'implémentation publique et open source du système X en version 11. (Cf. X.org Wikipedia Article ou X.org pour les détails.) Pour résumer, si vous voulez une interface graphique, vous voulez Xorg.
Installer Xorg
Avant de commencer, assurez vous que :
- pacman est configuré et a jour. - Connaitre le driver utilisé par votre carte graphique. (nVidia ou ATi par exemple)
Pour commencer installez l'intégrale du groupe "xorg" :
# pacman -S xorg
Le driver 'vesa', qui est compatible avec pratiquement tout les chipsets graphiques. C'est plutôt une solution de secours (Pas d'accélération, et peu de résolutions disponibles). Ensuite nous installerons un driver plus adapté si possible. Cette commande liste l'ensemble des drivers open-source disponibles :
# pacman -Ss xf86-video
Cherchez le bon driver pour votre carte graphique et installez le avec pacman -S.
Pour savoir quelle carte est installée dans votre ordinateur, installez hwd (pacman -S hwdetect) ou community/lshw :
$ hwd -s
ou :
$lshw -short
ou :
$ lspci | grep "VGA"
Configurer xorg
Avant de lancer xorg, vous devez le configurer afin qu'il connaisse les caractéristiques de votre carte graphique, écran, souris et clavier. Il existe plusieurs méthodes pour automatiser le processus :
Sans xorg.conf
La dernière version de Xorg peut détecter le matériel avec l'aide de HAL. Ainsi, l'utilisation d'un fichier xorg.conf devient optionnelle. Il peut être intéressant de commencer sans le fichier xorg.conf, et d'ajouter uniquement les sections nécessaires.
Comme xorg a besoin de hal, installez le, si ce n'est pas déjà fait :
# pacman -S hal
Ajoutez dans la liste des DAEMONS= du fichier {Filename|/etc/rc.conf}} :
Démarrez hal :
# /etc/rc.d/hal start
Démarrez X :
$ startx
ou
$ xinit
Si X démarre et que vous voulez un fichier xorg.conf de base, il est possible de le créer à partir du fichier Xorg.0.log
Si il n'a pas détecté de driver propriétaire, ajoutez un fichier xorg.conf minimaliste similaire a :
Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 EndSection Section "Files" FontPath "/usr/share/fonts/local/" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce Go 7300" EndSection Section "Screen" Identifier "Screen0" Device "Device0" EndSection
Définir un clavier autre qu'américain dans xorg.conf
# cp /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi /etc/hal/fdi/policy/
Puis ouvrez /etc/hal/fdi/policy/10-keymap.fdi et modifiez "us" dans input.xkb.layout
selon vos besoins (fr pour un clavier français) et, si nécessaire, éditez aussi input.xkb.variant
(avec par exemple 'oss').
La commande
# setxkbmap fr
(avec le layout de votre clavier à la place de fr) exécuté dans X permet de changer la disposition de votre clavier. Pour faire en sorte que ce soit permanent vous pouvez ajouter cette commande dans le fichier ~/.xinitrc (avant de lancer le gestionnaire de fenêtre)
hwd
A priori la façon la plus simple de faire fonctionner rapidement Xorg est d'utiliser hwd, un outils écrit par les utilisateur de la communauté Arch Linux. Pour résumer c'est un outil qui permet de détecter le matériel qui a plusieurs utilisations dont l'une d'elle est de configurer le serveur X. Heureusement, hwd est beaucoup plus simple que xorgconf et ne requiert aucun paramètre.
Pour commencer installer le paquet hwd a partir de AUR.
Puis, en tant que root, lancez simplement la commande suivante pour générer un fichier xorg.conf :
# hwd -xa
Ceci va écraser tout fichier /etc/X11/xorg.conf existant avec un ensemble de paramètres basés sur le materiel que hwd a détecté.
Sinon, vous pouvez générer un fichier d'exemple (/etc/X11/xorg.conf.hwd) sans écraser vos paramètres. Pour cela, lancez hwd avec le paramètre -x :
# hwd -x
Exemple :
/etc/X11/xorg.conf.ati /etc/X11/xorg.conf.vesa
Une fois votre fichier prêt, renommez le en 'xorg.conf'. Si vous n'êtes pas sure de vous essayer d'abord la version 'vesa'.
Par exemple :
# mv /etc/X11/xorg.conf.vesa /etc/X11/xorg.conf
AD: Selon mon expérience hwd crée un fichier XF86Config-4 et si il n'a pas de fichier xorg.conf présent, Xorg l'utilise automatiquement.
Xorg -configure
Vous pouvez aussi utiliser :
# Xorg -configure
Ou
# X -configure
la commande crée un fichier xorg.conf.new dans le répertoire courant. Vous pouvez le tester en faisant :
# X -config ./xorg.conf.new
Puis copier le en tant que /etc/X11/xorg.conf.
nvidia-xconfig
Les possesseurs de cartes nvidia peuvent aussi utiliser :
# nvidia-xconfig
quand les drivers nvidia officiels sont installé.
Commentez la ligne :
Load "type1"
dans la section Module car les dernière versions de xorg-server n'incluent plus les polices type1 (Complètement remplacés par freetype).
A partir du fichier Xorg.0.log
Si vous démarrez X sans aucun fichier xorg.conf, vous pourrez trouver la configuration par défaut dans le fichier /var/log/Xorg.0.log. Copiez le texte entre les lignes :
(==) --- Start of built-in configuration ---
et
(==) --- End of built-in configuration ---
dans votre nouveau fichier xorg.conf.
Éditer xorg.conf
Vous souhaiterez peut-être modifier la configuration générée. Pour cela ouvrez le fichier xorg avec votre éditeur de texte favori (Nécessite d'être root) :
# vim /etc/X11/xorg.conf
ou utiliser le "Configuration toolkit" d'Xorg (xorg-server version < 1.6) :
# xorgcfg -textmode
Paramètres de l'écran
Peut-être souhaiterez vous utiliser d'autre paramètres que ceux proposé par défaut (une résolution plus basse, par exemple ?) a moins que Xorg n'ai pas réussi a définir les capacités de votre écran. Dans tous les cas vous devriez consulter le manuel de votre écran afin de connaitre les valeurs nécessaires.
Les paramètres suivant sont a définir dans la section "monitor" :
Horizontal Sync
HorizSync 28-64
Refresh Rate
VertRefresh 60
Ceux-ci dans la section "Screen" :
Color Depth
Depth 24
Resolution
Modes "1280x1024" "1024x768" "800x600"
Configuration de plusieurs écrans
La façon la plus simple de mettre en place d'autres écrans est d'utiliser xrandr après le démarrage de X. Commencez par exécuter (à partir de n'importe quel compte) :
xrandr -q
Cette commande va lister les sortie vidéos ainsi que quelques informations les concernant. Imaginons que vos sorties soient VGA-0, DVI-0 et S-Video. Pour fusionner les écrans utilisant DVI-0 et VGA-0, lancez :
xrandr --output DVI-0 --right-of VGA-0
Si cette commande fonctionne, ajoutez la dans votre fichier xinitrc.
Configuration du clavier
Xorg peut ne pas détecter votre clavier correctement. La disposition, ou le modèle du clavier peuvent ne pas être définis correctement.
Pour avoir la liste complète des modèles, dispositions, variantes et options, ouvrez :
/usr/share/X11/xkb/rules/xorg.lst
Hotplug avec xorg-server 1.5
Normalement xorg-serveur 1.5 tente de configurer votre clavier en utilisant le driver xf86-input-evdev (Qui lui utilise dbus et hal) au lieu d'utiliser votre configuration dans xorg.conf. Ceci peut entrainer une mauvaise disposition du clavier. La façon la plus simple de contourner le problème et de désactiver le système de hotplug en ajoutant le section suivante à votre fichier xorg.conf :
Section "ServerFlags" Option "AutoAddDevices" "False" EndSection
Pour plus d'informations : Xorg input hotplugging.
Disposition du clavier
To change the keyboard layout, use the XkbLayout option in the keyboard InputDevice section. For example, if you have a keyboard with English layout:
Option "XkbLayout" "gb"
To be able to easily switch keyboard layouts, for example between a US and a Swedish layout use this instead:
Option "XkbLayout" "us, se" Option "XkbOptions" "grp:caps_toggle"
This makes your Caps Lock key switch between the different layouts. This is mainly useful if you don't run a Desktop Environment which takes care of keyboard layouts for you.
Modèle de clavier
Pour changer le modèle de clavier, utilisez l'option dans la section clavier InputDevice. Par exemple, si vous avez un "Clavier Multimedia Sans-Fil Microsoft" :
Option "XkbModel" "microsoftmult"
Des Soucis avec votre clavier Apple ?
More information can be found here.
Display Size/DPI
In order to get correct sizing for fonts, the display size must be set for your desired DPI.
First thing you may try is Xorg autodetection of display size and DPI settings with DDC.
In /etc/X11/xorg.conf:
... Section "Module" # support for Data Display Channel. Allows to query the monitor capabilities via the video card Load "ddc" # serial bus over which you speak the ddc protocol to get info from the monitor Load "i2c" ... Section Screen ... DefaultColorDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection ...
And do not write any Modeline or DisplaySize settings. Sometimes it works fine, otherwise you need to set up it manualy.
One way to set it up is to pass an argument directly to the X (Xorg) binary. In /etc/X11/xinit/xserverrc add the "-dpi 96" part as follows:
exec /usr/bin/X -nolisten tcp -dpi 96
Alternatively, going back to the /etc/X11/xorg.conf file, in the section Monitor put in your display size in mm:
Section "Monitor" ... DisplaySize 336 252 # 96 DPI @ 1280x960 ... EndSection
The formula for calculating the DisplaySize values is Width (in inches) x 25.4 / DPI and Height (in inches) x 25.4 / DPI. If you're running Xorg with a resolution of 1024x768 and want a DPI of 96, use 1024 x 25.4 / 96 and 768 x 25.4 / 96. Round numbers down. (xorg expects width/height specifications to be given in milimeters. There are 25.4 milimeters per inch, thus the need to multiply by 25.4)
# calc: (x|y)pixels * 25.4 / dpi # DisplaySize 168 126 # 96 DPI @ 640x480 # DisplaySize 210 157 # 96 DPI @ 800x600 # DisplaySize 269 201 # 96 DPI @ 1024x768 # DisplaySize 302 227 # 96 DPI @ 1152x864 # DisplaySize 336 252 # 96 DPI @ 1280x960 # DisplaySize 336 210 # 96 DPI @ 1280x800 (non 4:3 aspect) # DisplaySize 339 271 # 96 DPI @ 1280x1024 (non 4:3 aspect) # DisplaySize 370 277 # 96 DPI @ 1400x1050 # DisplaySize 380 238 # 96 DPI @ 1440x900 (non 4:3 aspect) # DisplaySize 420 315 # 96 DPI @ 1600x1200 # DisplaySize 444 277 # 96 DPI @ 1680x1050 (non 4:3 aspect) # DisplaySize 506 315 # 96 DPI @ 1920x1200 (non 4:3 aspect)
In case X ignores your DisplaySize setting (known bug) add the following line in the Device section.
Option "NoDDC" "true"
For nVidia drivers you may have to disable automatic detection of DPI to set it manually. There is also an easier way to set DPI on these cards. Either or both of the following lines can be set in the device section for your nVidia card.
Option "UseEdidDpi" "false" Option "DPI" "96 x 96"
If X still ignores your DPI settings, and you have an RandR compliant video driver, you can use
xrandr --dpi 96
to manually set the DPI. You can add that command to your .xinitrc to have the DPI settings applied when you start X manually, and if you are using a display manager, like KDM, you can add it to your display manager's X statup file. For KDM, that would be somewhere like /usr/share/config/kdm/Xstartup.
Results can be checked by issuing the following command, which should return 96x96 dots per inch if you set DPI @ 96:
$ xdpyinfo | grep -B1 dot
Drivers propriétaires
Si vous souhaitez utiliser des drivers propriétaires, assurez-vous d'abord que le serveur X tourne correctement. Xorg devrait tourner de manière fluide sans les drivers officiels, qui sont utilisés pour des jeux avec accélération 3D, des configuration de dual-screen, ou encore des sorties TV. Référez-vous aux articles NVIDIA ou ATI suivent votre carte graphique pour l'installation de ces drivers.
Fonts
There some tips for setting up fonts in Xorg Font Configuration.
Sample Xorg.conf Files
Anyone who has an Xorg.conf file written up that works, go ahead and post a link to it here for others to look at! Please don't inline the entire conf file; upload it somewhere else and link. Thanks!
- raskolnikov (via unichrome and synaptics drivers): http://athanatos.free.fr/Arch/xorg.conf
- Mr.Elendig (nvidia with composite and "stuff") http://arch.har-ikkje.net/configs/etc/X11/xorg.conf
Running Xorg
This is done simply by typing:
$ startx
or
$ xinit
The default X environment is rather bare, and you will typically seek to install window managers or desktop environments to supplement X.
To test the config file you have created:
$ X -config <your config file>
If a problem occurs, then view the log at /var/log/Xorg.0.log. Be on the lookout for any lines beginning with (EE) which represent errors, and also (WW) which are warnings that could indicate other issues.
Please Note: Using startx or xinit requires a ~/.xinitrc file, so that X knows what to run when it starts. Your best option is to copy /etc/skel/.xinitrc to your home directory and edit it. Comment out the exec lines you don't want, and add or uncomment one for the WM you want to use. If you are using GNOME it is best to start GNOME through gdm to avoid HAL permission problems.
In addition, you can also install twm and xterm (via pacman), which will be used as a fallback if ~/.xinitrc does not exist (as stated in /etc/X11/xinit/xinitrc).
X startup (/usr/bin/startx) tweaking
For X's option reference see:
$ man Xserver
The following options have to be appended to the variable "defaultserverargs" in the /usr/bin/startx file:
- Prevent X from listening on tcp:
-nolisten tcp
- Getting rid of the gray weave pattern while X is starting and let X set a black root window:
-br
- Enable deferred glyph loading for 16 bit fonts:
-deferglyphs 16
Note: If you start X with kdm, the startx script does not seem to be executed. X options must be appended to the variable "ServerArgsLocal" or "ServerCmd" in the /usr/share/config/kdm/kdmrc file. By default kdm options are:
ServerArgsLocal=-nolisten tcp ServerCmd=/usr/bin/X
Changes with modular Xorg
Most Common Packages
Make sure you install drivers for mouse, keyboard and videocard. For mouse and keyboard, xf86-input-keyboard and xf86-input-mouse should get installed. Other xf86-input-* packages are available for different input devices.
For the videocard, find out which driver is required and install the right xf86-video-* package. ATI and Nvidia users may wish to install the non-free drivers for their hardware instead (NVIDIA, ATI).
To install all drivers in one run, the xorg-input-drivers and xorg-video-drivers are available.
OpenGL 3D Acceleration
X.Org 7.0 on Arch Linux uses a modular design for mesa, the OpenGL rendering system. Several implementations are available:
- libgl-dri: Open-source DRI OpenGL implementation. Falls back to software rendering when no DRI driver is installed
- some other driver providing libGL (ati, nvidia)
When pacman installs an application that needs mesa, it will install one of these packages. To be sure about the right library for your setup, install the library you want prior to installing Xorg. Installing the right package afterwards is also possible, though this gives some dependency errors sometimes, which can be ignored with the -d switch.
Glxgears et Glxinfo
ces applications sont incluses dans le paquet mesa.
Changed paths (and configuration)
See this entry for additional upgrade info: http://www.archlinux.org/blog/2006/01/02/how-to-upgrade-xorg/
Modular X.Org 7 installs everything in /usr, where the older versions installed in /usr/X11R6. Several configuration files need updates:
- /etc/X11/xorg.conf
- Fontpaths live in /usr/share/fonts now
- RGB database is in /usr/share/X11/rgb
- Module path is /usr/lib/xorg/modules
Also note that some X configuration tools might stop working. The easiest way to configure X.org is by installing the correct driver packages and running Xorg -configure, which results in a xorg.conf.new which only needs modification in the resolutions, mouse configuration and keyboard layouts.
Some packages have hard-coded references to /usr/X11R6. These packages need fixing. In the meantime, look what packages install files in /usr/X11R6, uninstall those, make a symlink from /usr to /usr/X11R6 and reinstall the affected packages. Another option is to move the contents of /usr/X11R6 to /usr and make the symlink.
Or you can just add a second module path via:
ModulePath "/usr/X11R6/lib/modules"
This works e.g. for Nvidia 76.76.
Troubleshooting
Blank screen after startx
Check if your user are in hal and dbus group. If not type this command's: gpasswd -a user hal gpasswd -a user dbus And after this startx.
Xorg's Common User Problems
If you are having trouble with xorg, it won't start or the screen is just black, the keyboard and mouse isn't working. Then first take this simple steps:
- did i run any Xorg configure script? ( xorg -Configure )
- did i looked into the log? ( /var/log/Xorg.0.log ) and if you are in irc looking for help paste the log.
pacman -S wgetpaste && wgetpaste /var/log/Xorg.0.log
- did i start hal or dbus ? - keyboard mouse doesn't work??
pacman -S xf86-input-{mouse,keyboard}
- this ATI video card is giving me a headache! Take a look at the ATI wiki, ATI isn't famous for their drivers so if you are considering buying i new pc take a good look at the graphic card.
Xorg "can't see" the resolutions your monitor supports
I found myself in a situation where if I used one of my monitors (a gnr ts902), Xorg would only present me with the options 640x480 and 320x480 which of course was less than I desired. After a lot of research I found through read-edid (in AUR) that part of my EDID was corrupt and so I could only read my HorizSync with read-edid. This fortunately was enough and after adding the right HorizSync line to the xorg.conf's Monitor section (I didn't have to add VertRefresh) I restarted X to see the right resolution :)
note: I'm not sure if
Option "ModeValidation" "NoEdidModes" Option "UseEdid" "false"
in Device section of xorg.conf are needed as well; too lazy now to test without them :)
To switch between layouts with Alt+Shift:
Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
A Quick Fix for the Bitstream-Vera Conflict
If you see a message that ttf-bitstream-vera conflicts with xorg:
- Exit the pacman session by answering no.
- Run
pacman -Rd xorg
- Run
pacman -Syu
- Run
pacman -S xorg
- Update your paths in /etc/X11/xorg.conf
A Quick Fix for file conflicts in /usr/include
If you see messages about file conflicts in /usr/include/X11 and /usr/include/GL:
- Run
rm /usr/include/{GL,X11}
- Run
pacman -Su
The symlinked directories removed by this operation are replaced by real directories in the new xorg package, causing these file conflicts to appear.
libgl-dri conflicts
(Note below, that nvidia-legacy has been replaced by nvidia-71xx or nvidia-96xx. See here for further details of which driver to use.)
If you get a message similar to:
:: libgl-dri conflicts with nvidia-legacy. Remove nvidia-legacy? [Y/n]
this is due to the multiple OpenGL implementations explained in the OpenGL section above - pacman is attempting to install libgl-dri to satisfy this dependency, but also trying to upgrade your existing video driver, and they conflict. To solve, try:
- Updating your video driver before a full system update:
# pacman -S nvidia-legacy # pacman -Syu
Or, if that doesn't work,
- Remove your existing video driver, do the update, then reinstall your driver:
# pacman -Rd nvidia-legacy # pacman -Syu # pacman -S nvidia-legacy :: nvidia-legacy conflicts with libgl-dri. Remove libgl-dri? [Y/n] Y
Mouse wheel not working
The "Auto" protocol doesn't seem to work properly in Xorg 7 any more. In the InputDevice section for your mouse, change:
Option "Protocol" "auto"
to
Option "Protocol" "IMPS/2"
or
Option "Protocol" "ExplorerPS/2"
If you were using "Auto" to configure your touchpad mouse (and its mouse wheel) you'll have to start using the "synaptics" driver, instead. The mouse wheel will be included on the right-hand area of the touchpad, then.
In 'Section "Module"' add:
Load "synaptics"
In 'Section "InputDevice"' add/change:
Driver "synaptics" Protocol "auto-dev"
Read man synaptics for more information.
Touchpad mouse taps not working
Previous versions of Xorg 7 allowed you to use the "Auto" protocol to configure your mouse, and tapping was enabled, too. Now you have to specify the driver, and explicitly enable tapping.
In 'Section "Module"' add:
Load "synaptics"
In 'Section "InputDevice"' add/change:
Driver "synaptics" Protocol "auto-dev" Option "TapButton1" "1" Option "TapButton2" "2" Option "TapButton3" "3"
And read man synaptics.
Extra mouse buttons not working
USB Mice users should read Get_All_Mouse_Buttons_Working.
Intellimouse (ExplorerPS/2) users might find their scroll and side buttons aren't behaving as they used to. Previously xorg.conf needed:
Option "Buttons" "7" Option "ZAxisMapping" "6 7"
and users also had to run xmodmap to get the side buttons working with a command like:
xmodmap -e "pointer = 1 2 3 6 7 4 5"
Now xmodmap is no longer required. Instead, make xorg.conf look like this:
Option "Buttons" "5" Option "ZAxisMapping" "4 5" Option "ButtonMapping" "1 2 3 6 7"
and the side buttons on a 7-button Intellimouse will work like they used to, without needing to run xmodmap.
Keyboard problems
Problems with switching to tty1
Auto-generated xorg.conf files may cause you problems. If you cannot get to tty1 by holding CTRL-ALT and pressing F1 or cannot get the £ sign for gb people, check to see if the following entries are in your /etc/X11/xorg.conf:
Option "XkbLayout" "uk" #"uk" is not a real layout, look in /usr/share/X11/xkb/symbols/ for a list of real ones. #Try "gb" if you want a UK keyboard layout Option "XkbRules" "xfree86" #this should be "xorg" Option "XkbVariant" "nodeadkeys" #This line is also known to cause the problems described, try commenting it out.
Some keyboard layouts have changed. I wondered why:
- I wasn't able to Ctrl+Alt+Fx to switch to console
- I wasn't able to use layouts
The problem was that the sk_qwerty layout doesn't exist anymore. I had to replace
Option "XkbLayout" "us,sk_qwerty"
with
Option "XkbLayout" "us,sk" Option "XkbVariant" ",qwerty"
Another thing to look for if your keyboard isn't properly functioning is the XkbRules option:
You'll need to change
Option "XkbRules" "xfree86"
to
Option "XkbRules" "xorg"
AltGR (Compose Key) not working properly
If, after the update, you can't use the AltGr key as expected any more, try adding this to your keyboard section:
Option "XkbOptions" "compose:ralt"
This is not the correct way to activate the AltGr Key on a German keyboard (for example, to use the '|' and '@' keys on German keyboards). Just choose a valid keyboard variant for it to work again, for example (the example is for a German keyboard):
Option "XkbLayout" "de" Option "XkbVariant" "nodeadkeys"
The solutions above don't work on an Italian keyboard. To activate the AltGr key on an Italian keyboard make sure you have the following lines set up properly:
Driver "kbd" Option "XkbRules" "xorg" Option "XkbVariant" ""
This might still not be enough for a swedish keyboard. Try the above, but with lv3 instead of compose. (Thank you wyvern!) That is:
Option "XkbLayout" "se" Option "XkbVariant" "nodeadkeys" Option "XkbOptions" "lv3:ralt_switch"
Can't set qwerty layouts using the setxkbmap command
After the update, there aren't qwerty layouts as for example sk_qwerty. If you want to switch your present keyboard layout to any qwerty keyboard layout use this command:
$ setxkbmap NAME_OF_THE_LAYOUT qwerty
e.g.: for sk_qwerty use:
$ setxkbmap sk qwerty
After the update, trying the above command I had this message "Error loading new keyboard description". I find out that the xserver doesn't have the rights to write, execute, read in the directory /var/tmp So give the permissions to that directory. Restart the xserver and you will have your deadkeys back! Don't believe? Try out the code e.g.: it layout
$ setxkbmap -layout it
Setup French Canadian (old ca_enhanced) layout
With disabled hotplugging
Since the new Xorg changed the way it deals with keyboards, the following method will only work if you disable "hotplugging" : http://wiki.archlinux.org/index.php/Xorg_input_hotplugging
With Xorg7, "ca_enhanced" is no more. You have to do a little trick to get the same layout that you are used to: Switch the old:
Option "XkbLayout" "ca_enhanced"
To:
Option "XkbLayout" "ca" Option "XkbVariant" "fr"
It will be similar with other layout, I presume. You can refer to Gentoo HowTo there: http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml
Workaround
I use a workaround so that I don't have to manually change the HAL fdi policies, as this is the new way of dealing with keymaps with the new Xorg. I use "setxkbmap" : http://wiki.archlinux.org/index.php/Xorg_input_hotplugging#Using_setxkbmap
Change the X keyboard layout to french canadian with this command:
#setxkbmap ca -variant fr
To make it change automatically, you can try this:
Created the file
~.config/autostart/keymap.desktop
and added this to it:
[Desktop Entry] Encoding=UTF-8 Version=0.9.4 Type=Application Name=Keymap French Canadian Comment= Exec=setxkbmap ca -variant fr StartupNotify=false Terminal=false Hidden=false
It works at least for XFCE4 and LXDE.
Missing libraries
- Help! I get an error message running my favourite app saying "libXsomething" doesn't exist!
In most cases, all you need to do is take the name of the library (eg libXau.so.1), convert it all to lowercase, remove the extension, and pacman for it:
# pacman -S libxau
This will install the library you're missing, and all will be well again!
la compilation/installation de certains paquets échoue en raison du manque d' "includes X11"
Réinstallez simplement les paquets "xproto" et "libx11", même s'ils sont déjà installés.
Unable to load font '(null)'
- Some programs don't work and say unable to load font `(null)'.
These packages would like some extra fonts. Some programs only work with bitmap fonts. Two major packages with bitmap fonts are available, xorg-fonts-75dpi and xorg-fonts-100dpi. You don't need both; one should be enough. To find out which one would be better in your case, try this:
$ xdpyinfo | grep resolution
and grab what is closer to you (75 or 100 instead of XX)
# pacman -S xorg-fonts-XXdpi
Après un mise à jour du server xorg 1.5, la console de KDE4 crash, et/ou les icônes du systray disparaissent en cas de clic droit
Remplacez la ligne
Option "BackingStore" "True"
par
Option "BackingStore" "False"
dans votre fichier /etc/X11/xorg.conf.
Updating from testing version to extra (missing files)
If you've updated from Xorg 7 in testing to Xorg 7 in extra and are finding that many files seem to be missing (including startx, /usr/share/X11/rgb.txt, and others), you may have lost many files due to the xorg-clients package splitting from a single package into many smaller sub packages.
You need to reinstall all the packages that are dependencies of xorg-clients:
# pacman -S xorg-apps xorg-font-utils xorg-res-utils xorg-server-utils \ xorg-twm xorg-utils xorg-xauth xorg-xdm xorg-xfs xorg-xfwp \ xorg-xinit xorg-xkb-utils xorg-xsm
This should fix the problem.
Problem with MIME types in various desktop environments
If you noticed icons missing and can't click-open files in desktop environments, add the following lines to /etc/profile or your preferred init script and reboot.
XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/share export XDG_DATA_DIRS
DRI stops working with Matrox cards
If you use a Matrox card and DRI stops working after upgrading to xorg7, try adding the line
Option "OldDmaInit" "On"
to the Device section that references the video card in xorg.conf.
Cannot start any clients under Xephyr
The client connections are rejected by the X server's security mechanism, you can find a complete explanation and solution in [1].
Cannot start X clients as root using "su"
If you're getting "Client is not authorized to connect to server", try adding the line
session optional pam_xauth.so
to the file /etc/pam.d/su. pam_xauth will properly set environment variables and handle xauth keys.
Cannot run in frambuffer mode
Si X échoue avec le log suivant :
(WW) Falling back to old probe method for fbdev (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so (II) Module fbdevhw: vendor="X.Org Foundation" compiled for 1.6.1, module version = 0.0.2 ABI class: X.Org Video Driver, version 5.0 (II) FBDEV(1): using default device Fatal server error: Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
alors désinstallez simplement le paquet xf86-video-fbdev
.
Ctrl-Alt-Backspace ne kill pas X
Modification du fichier /etc/X11/xorg.conf
Les nouvelles versions de xorg désactivent la combinaison Ctrl+Alt+Backspace par défaut.Vous pouvez l'activer en ajoutant la ligne suivante dans votre /etc/X11/xorg.conf
Option "XkbOptions" "terminate:ctrl_alt_bksp"
dans la section InputDevice pour clavier.
If you use input hotplugging
If you are using hal to manage your keyboard, you must add the following to /etc/hal/fdi/policy/10-keymap.fdi to enable this behavior. If that file does not exist, copy it from the template at /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi
<merge key="input.xkb.options" type="string">terminate:ctrl_alt_bksp</merge>
Restart hal after making the modification.
Another way is to add the following line to ~/.xinitrc
setxkbmap -option terminate:ctrl_alt_bksp
Disabling Xorg before the GUI login
If Xorg is set to boot up automatically and for some reason you need to prevent it from starting up before the login/display manager appears (if your rc.conf file is misconfigured and Xorg does not recognize your mouse or keyboard input, for instance), there are two ways. From the grub menu you can specify the runlevel in the kernel line by adding a number to the end of the kernel line specifying the run level you want. The following example sets the run level to 3:
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/..ro 3
If you have not only misconfigured rc.conf to make Xorg unusable, but you have also set the grub menu wait time to zero, or cannot otherwise use grub to prevent Xorg from booting, you must use the Arch live CD. Boot up the live CD and login as root. You need a mount point, such as /mnt, and you need to know the name of the partition you want to mount. You can use the command
fdisk -l
as root to see your partitions. Usually the one you want will be like /dev/sda1. Then to mount this to /mnt use
mount /dev/sda1 /mnt
Then your filesystem will show up under /mnt. So your rc.conf file, for example, would be in /mnt/etc/rc.conf. From here you can delete the gdm module to prevent Xorg from booting up normally, or make any other necessary changes.
Liens
- Enabling a DM
- Start X at boot
- Xorg Font Configuration
- Proprietary Video Drivers
- Desktop Environment
- Get All Mouse Buttons Working
- Compiz Fusion