Inverser sens souris
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
je voudrais inverser les sens de la souris (droite et gauche, haut et bas) je me souviens que quelqu'un du forum m'avait donner la solution mais elle ne fonctionne plus
je vous met ce qu'il fallait mettre au temps de mandrake ou mandriva
dans le xorg
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/mouse"
Option "InvX" "on"
Option "InvY" "on"
EndSection
merci
Meuz Membre non connecté
-
- Voir le profil du membre Meuz
- Inscrit le : 06/08/2011
- Groupes :
Configuration du système, Périphériques d'entrée, Souris :
Inverser le défilement.
nic80 Membre non connecté
-
- Voir le profil du membre nic80
- Inscrit le : 06/08/2018
- Groupes :
-
Modérateur
Je pense qu' avec les versions récentes de Xorg, la section "Inputdevice" est ignorée.
Citation :INPUTDEVICE SECTION
The config file may have multiple InputDevice sections. Recent X servers employ HAL or udev backends for input device enumeration and input hotplugging. It is usually
not necessary to provide InputDevice sections in the xorg.conf if hotplugging is in use (i.e. AutoAddDevices is enabled). If hotplugging is enabled, InputDevice sections
using the mouse, kbd and vmmouse driver will be ignored.
Dans la section ServerFlags, il semble être possible de désactiver l' ajout automatique de périphériques ( donc basé sur les événements udev) pour que la section inputdevice soit prise en compte.
Citation :Option "AutoAddDevices" "boolean"
If this option is disabled, then no devices will be added from the HAL or udev backends. Enabled by default.
Mais dans ce cas, je suppose que tout périphérique ( ecran, clavier, souris, carte graphique doit être défini dans le fichier xorg).
edit: @Meuz , l'option inverser le défilement ne semble visiblement qu' inverser le défilement de page ( la "roulette"), je ne suis pas sur que ce soit ce qui soit recherché ( quand on déplace à droite le curseur va à gauche et quand on déplace vers le bas, la souris va vers le haut ?)
edit 2: visiblement le pilote mouse(drv) semble avoir été supprimé ( suppression du support Linux), au profit de evdev ( le paquet x11-input-evdev devrait donc être installé. Inconvénient rien ne dit que la numérotation evdev soit constante avec le temps/redémarrage. Une règle udev devrait donc probablement être définie pour être sur que ça ne change pas.
Édité par nic80 Le 20/02/2026 à 23h52
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
je ne voit pas cette option
voici mon xorg
Caché :
# File generated by XFdrake (rev 262502)
# **********************************************************************
# Refer to the xorg.conf man page for details about the format of
# this file.
# **********************************************************************
Section "ServerFlags"
AllowMouseOpenFail # allows the server to start up even if the mouse does not work
#DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching)
Option "DontZap" "False" # disable <Ctrl><Alt><BS> (server abort)
EndSection
Section "Module"
Load "v4l" # Video for Linux
EndSection
Section "Monitor"
Identifier "monitor1"
VendorName "Plug'n Play"
# Apple iMac modes
ModeLine "1024x768" 78.525 1024 1049 1145 1312 768 769 772 800 +hsync +vsync
ModeLine "800x600" 62.357 800 821 901 1040 600 601 604 632 +hsync +vsync
ModeLine "640x480" 49.886 640 661 725 832 480 481 484 514 +hsync +vsync
# Apple monitors tend to do 832x624
ModeLine "832x624" 57 832 876 940 1152 624 625 628 667 -hsync -vsync
# Apple PowerBook G3
ModeLine "800x600" 100 800 816 824 840 600 616 624 640 -hsync -vsync
# Apple TI Powerbook
ModeLine "1152x768" 78.741 1152 1173 1269 1440 768 769 772 800 +vsync +vsync
# Pismo Firewire G3
ModeLine "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync
# iBook2
ModeLine "1024x768" 65 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 17" Apple Studio Display
ModeLine "1024x768" 112.62 1024 1076 1248 1420 768 768 780 808 +hsync +vsync
# HiRes Apple Studio Display
ModeLine "1280x1024" 135 1280 1288 1392 1664 1024 1027 1030 1064
# Another variation
ModeLine "1280x1024" 134.989 1280 1317 1429 1688 1024 1025 1028 1066 +hsync +vsync
# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630
# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
EndSection
Section "Device"
Identifier "device1"
VendorName "Advanced Micro Devices, Inc. [AMD/ATI]"
BoardName "ATI Radeon HD 4870 and earlier"
Driver "ati"
Option "DPMS"
EndSection
Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultColorDepth 24
EndSection
Section "ServerLayout"
Identifier "layout1"
Screen "screen1"
EndSection
# **********************************************************************
# Refer to the xorg.conf man page for details about the format of
# this file.
# **********************************************************************
Section "ServerFlags"
AllowMouseOpenFail # allows the server to start up even if the mouse does not work
#DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching)
Option "DontZap" "False" # disable <Ctrl><Alt><BS> (server abort)
EndSection
Section "Module"
Load "v4l" # Video for Linux
EndSection
Section "Monitor"
Identifier "monitor1"
VendorName "Plug'n Play"
# Apple iMac modes
ModeLine "1024x768" 78.525 1024 1049 1145 1312 768 769 772 800 +hsync +vsync
ModeLine "800x600" 62.357 800 821 901 1040 600 601 604 632 +hsync +vsync
ModeLine "640x480" 49.886 640 661 725 832 480 481 484 514 +hsync +vsync
# Apple monitors tend to do 832x624
ModeLine "832x624" 57 832 876 940 1152 624 625 628 667 -hsync -vsync
# Apple PowerBook G3
ModeLine "800x600" 100 800 816 824 840 600 616 624 640 -hsync -vsync
# Apple TI Powerbook
ModeLine "1152x768" 78.741 1152 1173 1269 1440 768 769 772 800 +vsync +vsync
# Pismo Firewire G3
ModeLine "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync
# iBook2
ModeLine "1024x768" 65 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 17" Apple Studio Display
ModeLine "1024x768" 112.62 1024 1076 1248 1420 768 768 780 808 +hsync +vsync
# HiRes Apple Studio Display
ModeLine "1280x1024" 135 1280 1288 1392 1664 1024 1027 1030 1064
# Another variation
ModeLine "1280x1024" 134.989 1280 1317 1429 1688 1024 1025 1028 1066 +hsync +vsync
# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630
# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
EndSection
Section "Device"
Identifier "device1"
VendorName "Advanced Micro Devices, Inc. [AMD/ATI]"
BoardName "ATI Radeon HD 4870 and earlier"
Driver "ati"
Option "DPMS"
EndSection
Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultColorDepth 24
EndSection
Section "ServerLayout"
Identifier "layout1"
Screen "screen1"
EndSection
Merci
nic80 Membre non connecté
-
- Voir le profil du membre nic80
- Inscrit le : 06/08/2018
- Groupes :
-
Modérateur
Désolé mon édition s 'est intercallée entre temps...
Par défaut, AutoAddDevices est activé ( réglage par défaut). Partant du principe que l' option AutoAddDevices n' est pas définie dans la partie ServerFlags, cette valeur par défaut est utilisée.
Attention, si cette option est rajoutée manuellement, il est fort probable que le serveur X, ne démarre pas correctement (la modeline doit être supportée par l'écran et le pilote graphique doit être le bon ( ati ?).
Dans ce fichier une section InputDevice devrait être ajoutée pour supporter le clavier et la souris aussi. Sans clavier ni souris le serveur X sera incontrolable.
Les drivers mouse et keyboard ayant probablement disparus, dans cette section le pilote evdev devra probablement être utilisé.
Attention : Avant de faire quelconque modification, s' assurer de garder un fichier xorg.conf fonctionnel quelque part et/ou être en mesure de supprimer/renommer le fichier xorg.conf pour être sur que Xorg puisse démarrer en mode détection.
Édité par nic80 Le 21/02/2026 à 00h17
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
et oui déjà fait des essai avec pour résultat un écran noir avec un carré blanc en guise de curseur (limité dans les déplacement) mais fonctionne dans les directions souhaitées.
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
bon sa ne réagit plus depuis que j'ai mis evdev peut être oublié quelques choses!
voila mon xorg
Caché :
# File generated by XFdrake (rev 262502)
# **********************************************************************
# Refer to the xorg.conf man page for details about the format of
# this file.
# **********************************************************************
Section "ServerFlags"
Option "DontZap" "False" # disable <Ctrl><Alt><BS> (server abort)
AllowMouseOpenFail # allows the server to start up even if the mouse does not work
#DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching)
EndSection
Section "Module"
Load "v4l" # Video for Linux
EndSection
Section "Monitor"
Identifier "monitor1"
VendorName "Plug'n Play"
Option "PreferredMode" "1680x1050"
# Apple iMac modes
ModeLine "1024x768" 78.525 1024 1049 1145 1312 768 769 772 800 +hsync +vsync
ModeLine "800x600" 62.357 800 821 901 1040 600 601 604 632 +hsync +vsync
ModeLine "640x480" 49.886 640 661 725 832 480 481 484 514 +hsync +vsync
# Apple monitors tend to do 832x624
ModeLine "832x624" 57 832 876 940 1152 624 625 628 667 -hsync -vsync
# Apple PowerBook G3
ModeLine "800x600" 100 800 816 824 840 600 616 624 640 -hsync -vsync
# Apple TI Powerbook
ModeLine "1152x768" 78.741 1152 1173 1269 1440 768 769 772 800 +vsync +vsync
# Pismo Firewire G3
ModeLine "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync
# iBook2
ModeLine "1024x768" 65 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 17" Apple Studio Display
ModeLine "1024x768" 112.62 1024 1076 1248 1420 768 768 780 808 +hsync +vsync
# HiRes Apple Studio Display
ModeLine "1280x1024" 135 1280 1288 1392 1664 1024 1027 1030 1064
# Another variation
ModeLine "1280x1024" 134.989 1280 1317 1429 1688 1024 1025 1028 1066 +hsync +vsync
# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630
# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_120" 313.20 1680 1816 2000 2320 1050 1051 1054 1125 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_100" 256.20 1680 1808 1992 2304 1050 1051 1054 1112 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_85" 214.51 1680 1800 1984 2288 1050 1051 1054 1103 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_75" 188.07 1680 1800 1984 2288 1050 1051 1054 1096 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_60" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_50" 120.21 1680 1776 1952 2224 1050 1051 1054 1081 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_120" 284.04 1600 1728 1904 2208 1000 1001 1004 1072 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_100" 232.13 1600 1720 1896 2192 1000 1001 1004 1059 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_85" 194.21 1600 1712 1888 2176 1000 1001 1004 1050 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_75" 169.13 1600 1704 1880 2160 1000 1001 1004 1044 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_60" 133.14 1600 1704 1872 2144 1000 1001 1004 1035 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_50" 108.66 1600 1688 1856 2112 1000 1001 1004 1029 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_120" 229.75 1440 1552 1712 1984 900 901 904 965 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_100" 187.55 1440 1544 1704 1968 900 901 904 953 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_85" 156.79 1440 1536 1696 1952 900 901 904 945 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_75" 136.49 1440 1536 1688 1936 900 901 904 940 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_60" 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_50" 87.41 1440 1512 1664 1888 900 901 904 926 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_120" 181.21 1280 1376 1520 1760 800 801 804 858 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_100" 147.89 1280 1376 1512 1744 800 801 804 848 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_85" 123.38 1280 1368 1504 1728 800 801 804 840 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_75" 107.21 1280 1360 1496 1712 800 801 804 835 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_60" 83.46 1280 1344 1480 1680 800 801 804 828 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_50" 68.56 1280 1336 1472 1664 800 801 804 824 -HSync +Vsync
EndSection
Section "Device"
Identifier "device1"
VendorName "Advanced Micro Devices, Inc. [AMD/ATI]"
BoardName "ATI Radeon HD 4870 and earlier"
Driver "ati"
Option "DPMS"
EndSection
Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultColorDepth 24
Subsection "Display"
Depth 8
Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
EndSubsection
Subsection "Display"
Depth 15
Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
EndSubsection
Subsection "Display"
Depth 16
Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
EndSubsection
Subsection "Display"
Depth 24
Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
EndSubsection
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "evdev"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/mouse"
Option "InvX" "on"
Option "InvY" "on"
EndSection
Section "ServerLayout"
Identifier "layout1"
Screen "screen1"
EndSection
# **********************************************************************
# Refer to the xorg.conf man page for details about the format of
# this file.
# **********************************************************************
Section "ServerFlags"
Option "DontZap" "False" # disable <Ctrl><Alt><BS> (server abort)
AllowMouseOpenFail # allows the server to start up even if the mouse does not work
#DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching)
EndSection
Section "Module"
Load "v4l" # Video for Linux
EndSection
Section "Monitor"
Identifier "monitor1"
VendorName "Plug'n Play"
Option "PreferredMode" "1680x1050"
# Apple iMac modes
ModeLine "1024x768" 78.525 1024 1049 1145 1312 768 769 772 800 +hsync +vsync
ModeLine "800x600" 62.357 800 821 901 1040 600 601 604 632 +hsync +vsync
ModeLine "640x480" 49.886 640 661 725 832 480 481 484 514 +hsync +vsync
# Apple monitors tend to do 832x624
ModeLine "832x624" 57 832 876 940 1152 624 625 628 667 -hsync -vsync
# Apple PowerBook G3
ModeLine "800x600" 100 800 816 824 840 600 616 624 640 -hsync -vsync
# Apple TI Powerbook
ModeLine "1152x768" 78.741 1152 1173 1269 1440 768 769 772 800 +vsync +vsync
# Pismo Firewire G3
ModeLine "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync
# iBook2
ModeLine "1024x768" 65 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 17" Apple Studio Display
ModeLine "1024x768" 112.62 1024 1076 1248 1420 768 768 780 808 +hsync +vsync
# HiRes Apple Studio Display
ModeLine "1280x1024" 135 1280 1288 1392 1664 1024 1027 1030 1064
# Another variation
ModeLine "1280x1024" 134.989 1280 1317 1429 1688 1024 1025 1028 1066 +hsync +vsync
# TV fullscreen mode or DVD fullscreen output.
# 768x576 @ 79 Hz, 50 kHz hsync
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630
# 768x576 @ 100 Hz, 61.6 kHz hsync
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_120" 313.20 1680 1816 2000 2320 1050 1051 1054 1125 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_100" 256.20 1680 1808 1992 2304 1050 1051 1054 1112 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_85" 214.51 1680 1800 1984 2288 1050 1051 1054 1103 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_75" 188.07 1680 1800 1984 2288 1050 1051 1054 1096 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_60" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1680x1050_50" 120.21 1680 1776 1952 2224 1050 1051 1054 1081 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_120" 284.04 1600 1728 1904 2208 1000 1001 1004 1072 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_100" 232.13 1600 1720 1896 2192 1000 1001 1004 1059 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_85" 194.21 1600 1712 1888 2176 1000 1001 1004 1050 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_75" 169.13 1600 1704 1880 2160 1000 1001 1004 1044 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_60" 133.14 1600 1704 1872 2144 1000 1001 1004 1035 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1600x1000_50" 108.66 1600 1688 1856 2112 1000 1001 1004 1029 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_120" 229.75 1440 1552 1712 1984 900 901 904 965 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_100" 187.55 1440 1544 1704 1968 900 901 904 953 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_85" 156.79 1440 1536 1696 1952 900 901 904 945 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_75" 136.49 1440 1536 1688 1936 900 901 904 940 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_60" 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1440x900_50" 87.41 1440 1512 1664 1888 900 901 904 926 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_120" 181.21 1280 1376 1520 1760 800 801 804 858 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_100" 147.89 1280 1376 1512 1744 800 801 804 848 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_85" 123.38 1280 1368 1504 1728 800 801 804 840 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_75" 107.21 1280 1360 1496 1712 800 801 804 835 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_60" 83.46 1280 1344 1480 1680 800 801 804 828 -HSync +Vsync
# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x800_50" 68.56 1280 1336 1472 1664 800 801 804 824 -HSync +Vsync
EndSection
Section "Device"
Identifier "device1"
VendorName "Advanced Micro Devices, Inc. [AMD/ATI]"
BoardName "ATI Radeon HD 4870 and earlier"
Driver "ati"
Option "DPMS"
EndSection
Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultColorDepth 24
Subsection "Display"
Depth 8
Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
EndSubsection
Subsection "Display"
Depth 15
Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
EndSubsection
Subsection "Display"
Depth 16
Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
EndSubsection
Subsection "Display"
Depth 24
Modes "1680x1050" "1600x1000" "1440x900" "1280x800"
EndSubsection
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "evdev"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/mouse"
Option "InvX" "on"
Option "InvY" "on"
EndSection
Section "ServerLayout"
Identifier "layout1"
Screen "screen1"
EndSection
merci
nic80 Membre non connecté
-
- Voir le profil du membre nic80
- Inscrit le : 06/08/2018
- Groupes :
-
Modérateur
On est sur que /dev/mouse existe ?
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
que faut il mettre?
nic80 Membre non connecté
-
- Voir le profil du membre nic80
- Inscrit le : 06/08/2018
- Groupes :
-
Modérateur
Cela est compliqué à dire.
La souris est probablement sous un /dev/input/
En faisant un (en root) journalctl -b | grep -i event devrait permettre de savoir quel event est associé.
Ceci dit il faudrait regarder si /dev/input, il n' y a pas un périphérique mice ou mouse0 ( ce pourrait être là de ceux là ( et bien plus compréhensible que /dev/inout/eventX ( où X peut changer entre chaque démarrage)).
GPE GPE Membre non connecté
-
- Voir le profil du membre GPE GPE
- Inscrit le : 05/06/2011
- Groupes :
journalctl -b | grep -i event
Caché :
[root@MGA-9 chassin]# journalctl -b | grep -i event
févr. 21 16:33:57 MGA-9 kernel: Performance Events: AMD PMU driver.
févr. 21 16:33:57 MGA-9 kernel: ... fixed-purpose events: 0
févr. 21 16:33:57 MGA-9 kernel: ... event mask: 000000000000000f
févr. 21 16:33:57 MGA-9 kernel: hid: raw HID events driver (C) Jiri Kosina
févr. 21 16:33:57 MGA-9 kernel: device-mapper: uevent: version 1.0.3
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 445: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 446: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Argument invalide
févr. 21 16:34:07 MGA-9 acpid[707]: waiting for events: event logging is off
févr. 21 16:34:08 MGA-9 systemd-logind[739]: Watching system buttons on /dev/input/event1 (Power Button)
févr. 21 16:34:08 MGA-9 systemd-logind[739]: Watching system buttons on /dev/input/event0 (Power Button)
févr. 21 16:34:08 MGA-9 systemd-logind[739]: Watching system buttons on /dev/input/event3 (Logitech Wireless Keyboard PID:005d)
févr. 21 16:34:33 MGA-9 sddm-greeter[1428]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
févr. 21 16:35:45 MGA-9 org_kde_powerdevil[1736]: org.kde.powerdevil: Handle button events action could not check for screen configuration
févr. 21 18:23:40 MGA-9 diskdrake[7576]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 18:23:43 MGA-9 diskdrake[7576]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 18:25:41 MGA-9 diskdrake[27261]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 18:25:44 MGA-9 diskdrake[27261]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 18:44:25 MGA-9 kernel: perf: interrupt took too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
févr. 21 19:15:28 MGA-9 drakxservices[37780]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:15:29 MGA-9 drakxservices[37780]: running: /bin/systemctl --quiet is-active dm-event.socket
févr. 21 19:16:56 MGA-9 drakxservices[37780]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:17:08 MGA-9 drakxservices[38303]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:17:09 MGA-9 drakxservices[38303]: running: /bin/systemctl --quiet is-active dm-event.socket
févr. 21 19:17:44 MGA-9 drakxservices[38303]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:50:18 MGA-9 kernel: perf: interrupt took too long (3130 > 3128), lowering kernel.perf_event_max_sample_rate to 63500
févr. 21 19:52:24 MGA-9 drakfirewall[40028]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:53:22 MGA-9 drakfirewall[40028]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:59:39 MGA-9 drakxservices[40963]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:59:40 MGA-9 drakxservices[40963]: running: /bin/systemctl --quiet is-active dm-event.socket
févr. 21 20:00:38 MGA-9 drakxservices[40963]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 20:00:43 MGA-9 drakxservices[41391]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 20:00:44 MGA-9 drakxservices[41391]: running: /bin/systemctl --quiet is-active dm-event.socket
[root@MGA-9 chassin]#
févr. 21 16:33:57 MGA-9 kernel: Performance Events: AMD PMU driver.
févr. 21 16:33:57 MGA-9 kernel: ... fixed-purpose events: 0
févr. 21 16:33:57 MGA-9 kernel: ... event mask: 000000000000000f
févr. 21 16:33:57 MGA-9 kernel: hid: raw HID events driver (C) Jiri Kosina
févr. 21 16:33:57 MGA-9 kernel: device-mapper: uevent: version 1.0.3
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 445: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 446: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Argument invalide
févr. 21 16:34:05 MGA-9 (udev-worker)[560]: event4: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Argument invalide
févr. 21 16:34:07 MGA-9 acpid[707]: waiting for events: event logging is off
févr. 21 16:34:08 MGA-9 systemd-logind[739]: Watching system buttons on /dev/input/event1 (Power Button)
févr. 21 16:34:08 MGA-9 systemd-logind[739]: Watching system buttons on /dev/input/event0 (Power Button)
févr. 21 16:34:08 MGA-9 systemd-logind[739]: Watching system buttons on /dev/input/event3 (Logitech Wireless Keyboard PID:005d)
févr. 21 16:34:33 MGA-9 sddm-greeter[1428]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
févr. 21 16:35:45 MGA-9 org_kde_powerdevil[1736]: org.kde.powerdevil: Handle button events action could not check for screen configuration
févr. 21 18:23:40 MGA-9 diskdrake[7576]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 18:23:43 MGA-9 diskdrake[7576]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 18:25:41 MGA-9 diskdrake[27261]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 18:25:44 MGA-9 diskdrake[27261]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 18:44:25 MGA-9 kernel: perf: interrupt took too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
févr. 21 19:15:28 MGA-9 drakxservices[37780]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:15:29 MGA-9 drakxservices[37780]: running: /bin/systemctl --quiet is-active dm-event.socket
févr. 21 19:16:56 MGA-9 drakxservices[37780]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:17:08 MGA-9 drakxservices[38303]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:17:09 MGA-9 drakxservices[38303]: running: /bin/systemctl --quiet is-active dm-event.socket
févr. 21 19:17:44 MGA-9 drakxservices[38303]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:50:18 MGA-9 kernel: perf: interrupt took too long (3130 > 3128), lowering kernel.perf_event_max_sample_rate to 63500
févr. 21 19:52:24 MGA-9 drakfirewall[40028]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:53:22 MGA-9 drakfirewall[40028]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:59:39 MGA-9 drakxservices[40963]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 19:59:40 MGA-9 drakxservices[40963]: running: /bin/systemctl --quiet is-active dm-event.socket
févr. 21 20:00:38 MGA-9 drakxservices[40963]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 20:00:43 MGA-9 drakxservices[41391]: running: /bin/systemctl --quiet is-enabled dm-event.socket
févr. 21 20:00:44 MGA-9 drakxservices[41391]: running: /bin/systemctl --quiet is-active dm-event.socket
[root@MGA-9 chassin]#
alors j'ai mice , mouse0 et mouse1
merci
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie