Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

activation pavé numérique

kersaweol

Bonjour,

Ayant installé mate 16.04 sur l'ordi de mon fils, je cherche à activer le pavé numérique à l'allumage.

J'ai suivi la doc numlockx et après avoir installé numlockx, ne trouvant rien dédié à MATE, j'ai fait l'intervention indiquée "pour toute version" sur le fichier /etc/rc.local en ajoutant :

# Turn Numlock on for the TTYs:
for tty in /dev/tty[1-6]; do
    /usr/bin/setleds -D +num < $tty
done

mais ça n'a rien changé...

Merci par avance.

Skubu

Salut,

Tu utilises un "login manager" pour te connecter à ta session ?
Si oui, installe sddm, ce serait plus simple.

sudo apt install sddm
sudo systemctl stop gdm.service
sudo systemctl disable gdm.service
sudo systemctl enable sddm.service
sudo reboot

Puis, si pas configuré par défaut, ajouter dans /etc/sddm.conf

sudo nano /etc/sddm.conf

[General]
Numlock=on

sudo reboot

LukePerp

kersaweol a écritMerci par avance.

Bonjour,
Va dans Gestionnaire de paramètres / Clavier / agencement / bouton option / déroule divers options / décoche "état par défaut du pavé numérique"

kersaweol

@ Skubu : merci ça fonctionne mais c'est un poil lent...

@LukePerp : ton message est arrivé trop tard ; dommage car c'était certainement un procédé plus simple ?

Skubu

Possible, depuis l'abandon de SLiM, peu sont légers, et gdm ne gère pas cette option il me semble.
Je pensais que mate avait forké gdm en mdm ??

LXDM serait plus léger, en espérant que ça n'installe pas trop de dépendances.

kersaweol

Bonjour,

J'aimerais revenir à login manager, histoire d'essayer la méthode de LukePerp.

Comment procéder ?

Skubu

Salut,

Comme cela:

sudo systemctl stop sddm.service
sudo systemctl disable sddm.service
sudo systemctl enable gdm.service
sudo reboot

Je reste perplexe sur la solution proposée par LukePerp mais tu nous diras. 🙂

kersaweol

Merci Skubu .

J'ai un pb car dès que je valide les commandes ça ferme tout et un écran noir apparait...
Obligé de faire Ctrl+Alt+F1 et reboot.

Skubu

Et que se passe-t-il après le redémarrage ?

kersaweol

Je suis toujours sous sddm.

J'ai lu dans la doc sddm qu'avant de désactiver/supprimer sddm, il fallait installer le remplaçant...
Dans ce cas, ne faudrait-il pas faire en 1 :

sudo systemctl enable gdm.service

et ensuite virer le paquet sddm par synaptic ?

Je dis ça sans y connaître grand chose... Je pose la question pour simplement (et bien humblement !) faire avancer la question...

Skubu

sudo systemctl stop sddm.service

stoppe le service sddm.

sudo systemctl disable sddm.service

désactive le service sddm. Le laisser installé sur le système n'empêche pas d'en utiliser un autre.

sudo systemctl enable gdm.service

Réactive le service gdm. Le gestionnaire de session par défaut de mate.
On pourrait le lancer sans redémarrer avec

sudo systemctl start gdm.service

mais redémarrer permet de savoir si le changement est permanent.

~~~~~~~~

Après ça, sddm ne devrait plus intervenir. Si c'est le cas, donne le retour de

systemctl status sddm.service

systemctl status gdm.service

journalctl -b | grep -i systemd

kersaweol

Donc, comme déjà dit, la commande

sudo systemctl stop sddm.service

fait immédiatement fermer tout et --> écran noir avec curseur clignotant ; Ctrl+Alt+F1, sudo reboot etc

Résultat des commandes demandées :

fanfan@fanfan-VR630:~$ systemctl status sddm.service
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset: ena
   Active: active (running) since mer. 2017-11-22 06:02:58 CET; 9min ago
     Docs: man:sddm(1)
           man:sddm.conf(5)
  Process: 1255 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manage
 Main PID: 1258 (sddm)
   CGroup: /system.slice/sddm.service
           ├─1258 /usr/bin/sddm
           └─1265 /usr/lib/xorg/Xorg -nolisten tcp -auth /var/run/sddm/{1bda571b

nov. 22 06:04:19 fanfan-VR630 sddm-helper[2040]: [PAM] Authenticating...
nov. 22 06:04:19 fanfan-VR630 sddm-helper[2040]: [PAM] Preparing to converse...
nov. 22 06:04:19 fanfan-VR630 sddm-helper[2040]: [PAM] Conversation with 1 messa
nov. 22 06:04:19 fanfan-VR630 sddm-helper[2040]: pam_kwallet5(sddm:auth): (null)
nov. 22 06:04:20 fanfan-VR630 sddm-helper[2040]: [PAM] returning.
nov. 22 06:04:20 fanfan-VR630 sddm[1258]: Authenticated successfully
nov. 22 06:04:20 fanfan-VR630 sddm-helper[2040]: pam_kwallet5(sddm:setcred): pam
nov. 22 06:04:21 fanfan-VR630 sddm[1258]: Session started
nov. 22 06:04:21 fanfan-VR630 sddm[1258]: Auth: sddm-helper exited successfully
nov. 22 06:04:21 fanfan-VR630 sddm[1258]: Greeter stopped.
lines 1-21/21 (END)

à noter qu'après (END) il y a le curseur qui clignote et que rien ne se passe ensuite

fanfan@fanfan-VR630:~$ systemctl status gdm.service
● gdm.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
fanfan@fanfan-VR630:~$

fanfan@fanfan-VR630:~$ journalctl -b | grep -i systemd
nov. 22 06:02:39 fanfan-VR630 systemd-journald[243]: Runtime journal (/run/log/journal/) is 3.4M, max 27.7M, 24.2M free.
nov. 22 06:02:39 fanfan-VR630 kernel: random: systemd-udevd: uninitialized urandom read (16 bytes read)
nov. 22 06:02:39 fanfan-VR630 kernel: random: systemd-udevd: uninitialized urandom read (16 bytes read)
nov. 22 06:02:39 fanfan-VR630 systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Detected architecture x86.
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Set hostname to <fanfan-VR630>.
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Listening on Journal Socket (/dev/log).
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Listening on fsck to fsckd communication Socket.
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Listening on Journal Socket.
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Listening on Journal Audit Socket.
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Listening on udev Control Socket.
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
nov. 22 06:02:39 fanfan-VR630 systemd-journald[243]: Journal started
nov. 22 06:02:39 fanfan-VR630 systemd-modules-load[253]: Inserted module 'lp'
nov. 22 06:02:40 fanfan-VR630 systemd-modules-load[253]: Inserted module 'ppdev'
nov. 22 06:02:40 fanfan-VR630 systemd-modules-load[253]: Inserted module 'parport_pc'
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Started Load Kernel Modules.
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Mounting FUSE Control File System...
nov. 22 06:02:39 fanfan-VR630 systemd[1]: Starting Apply Kernel Variables...
nov. 22 06:02:40 fanfan-VR630 systemd[1]: Mounted FUSE Control File System.
nov. 22 06:02:40 fanfan-VR630 systemd[1]: Started Set console keymap.
nov. 22 06:02:40 fanfan-VR630 systemd[1]: Started Create Static Device Nodes in /dev.
nov. 22 06:02:40 fanfan-VR630 systemd[1]: Starting udev Kernel Device Manager...
nov. 22 06:02:40 fanfan-VR630 systemd[1]: Started Apply Kernel Variables.
nov. 22 06:02:45 fanfan-VR630 systemd[1]: Started udev Kernel Device Manager.
nov. 22 06:02:45 fanfan-VR630 systemd[1]: Starting Remount Root and Kernel File Systems...
nov. 22 06:02:45 fanfan-VR630 systemd[1]: Started Remount Root and Kernel File Systems.
nov. 22 06:02:45 fanfan-VR630 systemd[1]: Starting Load/Save Random Seed...
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Starting udev Coldplug all Devices...
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Reached target Local File Systems (Pre).
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Starting Flush Journal to Persistent Storage...
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Started Load/Save Random Seed.
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Started Flush Journal to Persistent Storage.
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Started udev Coldplug all Devices.
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Starting Show Plymouth Boot Screen...
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Started Show Plymouth Boot Screen.
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Created slice system-systemd\x2dbacklight.slice.
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:acpi_video0.
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:nv_backlight...
nov. 22 06:02:46 fanfan-VR630 systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:nv_backlight.
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Found device WDC_WD5000BEVT-80A0RT0 5.
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Found device WDC_WD5000BEVT-80A0RT0 6.
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Activating swap /dev/disk/by-uuid/485eab0c-ad52-488c-adb4-4e97ec139db2...
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Starting File System Check on /dev/disk/by-uuid/c3e8c4b7-cc9a-486f-952d-2ed7881a629d...
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Started File System Check Daemon to report status.
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Starting Load/Save RF Kill Switch Status...
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Activated swap /dev/disk/by-uuid/485eab0c-ad52-488c-adb4-4e97ec139db2.
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Reached target Swap.
nov. 22 06:02:48 fanfan-VR630 systemd[1]: Started Load/Save RF Kill Switch Status.
nov. 22 06:02:48 fanfan-VR630 systemd-fsck[515]: /dev/sda5 : récupération du journal
nov. 22 06:02:49 fanfan-VR630 systemd-fsck[515]: /dev/sda5 : propre, 10806/29188096 fichiers, 8679297/116724992 blocs
nov. 22 06:02:49 fanfan-VR630 systemd[1]: Started File System Check on /dev/disk/by-uuid/c3e8c4b7-cc9a-486f-952d-2ed7881a629d.
nov. 22 06:02:49 fanfan-VR630 systemd[1]: Mounting /home...
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Mounted /home.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Reached target Local File Systems.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Starting Enable support for additional executable binary formats...
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Starting Create Volatile Files and Directories...
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Starting Set console font and keymap...
nov. 22 06:02:50 fanfan-VR630 systemd-tmpfiles[599]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Starting LSB: AppArmor initialization...
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Started Create Volatile Files and Directories.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Starting Update UTMP about System Boot/Shutdown...
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Reached target System Time Synchronized.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Started Update UTMP about System Boot/Shutdown.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 598 (update-binfmts)
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Mounting Arbitrary Executable File Formats File System...
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Mounted Arbitrary Executable File Formats File System.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Started Enable support for additional executable binary formats.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Reached target Sound Card.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Started Set console font and keymap.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Created slice system-getty.slice.
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Received SIGRTMIN+20 from PID 350 (plymouthd).
nov. 22 06:02:50 fanfan-VR630 systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started LSB: AppArmor initialization.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Raise network interfaces...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Reached target System Initialization.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Listening on UUID daemon activation socket.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Daily Cleanup of Temporary Directories.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Socket activation for snappy daemon.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Listening on ACPID Listen Socket.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started ACPI Events Check.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started CUPS Scheduler.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Reached target Paths.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Timer to automatically refresh installed snaps.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Listening on D-Bus System Message Bus Socket.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Listening on CUPS Scheduler.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Listening on Socket activation for snappy daemon.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Reached target Sockets.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Reached target Basic System.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Accounts Service...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started ACPI event daemon.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Thermal Daemon Service...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting System Logging Service...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Permit User Sessions...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Save/Restore Sound Card State...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started CUPS Scheduler.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Regular background program processing daemon.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Modem Manager...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting LSB: daemon to balance interrupts for SMP systems...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting LSB: Speech Dispatcher...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Deferred execution scheduler.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started D-Bus System Message Bus.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Avahi DNS Configuration Daemon.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Login Service...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting LSB: automatic crash report generation...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Network Manager...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting LSB: Record successful boot for GRUB...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Snappy daemon...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started System Logging Service.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Permit User Sessions.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Save/Restore Sound Card State.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started LSB: Speech Dispatcher.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started LSB: automatic crash report generation.
nov. 22 06:02:51 fanfan-VR630 systemd-logind[786]: New seat seat0.
nov. 22 06:02:51 fanfan-VR630 systemd-logind[786]: Watching system buttons on /dev/input/event3 (Power Button)
nov. 22 06:02:51 fanfan-VR630 systemd-logind[786]: Watching system buttons on /dev/input/event0 (Lid Switch)
nov. 22 06:02:51 fanfan-VR630 systemd-logind[786]: Watching system buttons on /dev/input/event1 (Sleep Button)
nov. 22 06:02:51 fanfan-VR630 systemd-logind[786]: Watching system buttons on /dev/input/event5 (Video Bus)
nov. 22 06:02:51 fanfan-VR630 systemd-logind[786]: Watching system buttons on /dev/input/event2 (Power Button)
nov. 22 06:02:51 fanfan-VR630 systemd-logind[786]: Watching system buttons on /dev/input/event7 (MSI WMI hotkeys)
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Login Service.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Starting Set console scheme...
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Raise network interfaces.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Avahi mDNS/DNS-SD Stack.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Make remote CUPS printers available locally.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started LSB: daemon to balance interrupts for SMP systems.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started Set console scheme.
nov. 22 06:02:51 fanfan-VR630 systemd[1]: Started LSB: Record successful boot for GRUB.
nov. 22 06:02:52 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
nov. 22 06:02:52 fanfan-VR630 systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks...
nov. 22 06:02:52 fanfan-VR630 systemd[1]: Started Thermal Daemon Service.
nov. 22 06:02:52 fanfan-VR630 systemd[1]: Started Detect the available GPUs and deal with any system changes.
nov. 22 06:02:52 fanfan-VR630 systemd[1]: Starting Simple Desktop Display Manager...
nov. 22 06:02:52 fanfan-VR630 systemd[1]: Started Simple Desktop Display Manager.
nov. 22 06:02:52 fanfan-VR630 systemd[1]: Started Authenticate and Authorize Users to Run Privileged Tasks.
nov. 22 06:02:52 fanfan-VR630 systemd[1]: Started Accounts Service.
nov. 22 06:02:52 fanfan-VR630 systemd[1]: Started Modem Manager.
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Started Snappy daemon.
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Started Network Manager.
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Reached target Network.
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Started Unattended Upgrades Shutdown.
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Starting Network Manager Wait Online...
nov. 22 06:02:53 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Starting Network Manager Script Dispatcher Service...
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Started Network Manager Script Dispatcher Service.
nov. 22 06:02:53 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Starting Hostname Service...
nov. 22 06:02:53 fanfan-VR630 systemd[1]: Started Hostname Service.
nov. 22 06:02:54 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
nov. 22 06:02:54 fanfan-VR630 systemd[1]: Starting WPA supplicant...
nov. 22 06:02:54 fanfan-VR630 systemd[1]: Started WPA supplicant.
nov. 22 06:02:54 fanfan-VR630 systemd[1]: sddm.service: Main process exited, code=killed, status=11/SEGV
nov. 22 06:02:54 fanfan-VR630 systemd[1]: sddm.service: Unit entered failed state.
nov. 22 06:02:54 fanfan-VR630 systemd[1]: sddm.service: Triggering OnFailure= dependencies.
nov. 22 06:02:54 fanfan-VR630 systemd[1]: sddm.service: Failed with result 'signal'.
nov. 22 06:02:55 fanfan-VR630 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
nov. 22 06:02:55 fanfan-VR630 systemd[1]: Stopped Simple Desktop Display Manager.
nov. 22 06:02:55 fanfan-VR630 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
nov. 22 06:02:55 fanfan-VR630 systemd[1]: Started Detect the available GPUs and deal with any system changes.
nov. 22 06:02:55 fanfan-VR630 systemd[1]: Starting Simple Desktop Display Manager...
nov. 22 06:02:55 fanfan-VR630 systemd[1]: Started Simple Desktop Display Manager.
nov. 22 06:02:56 fanfan-VR630 systemd[1]: sddm.service: Main process exited, code=killed, status=11/SEGV
nov. 22 06:02:56 fanfan-VR630 systemd[1]: sddm.service: Unit entered failed state.
nov. 22 06:02:56 fanfan-VR630 systemd[1]: sddm.service: Triggering OnFailure= dependencies.
nov. 22 06:02:56 fanfan-VR630 systemd[1]: sddm.service: Failed with result 'signal'.
nov. 22 06:02:57 fanfan-VR630 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
nov. 22 06:02:57 fanfan-VR630 systemd[1]: Stopped Simple Desktop Display Manager.
nov. 22 06:02:57 fanfan-VR630 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
nov. 22 06:02:57 fanfan-VR630 systemd[1]: Started Detect the available GPUs and deal with any system changes.
nov. 22 06:02:57 fanfan-VR630 systemd[1]: Starting Simple Desktop Display Manager...
nov. 22 06:02:57 fanfan-VR630 systemd[1]: Started Simple Desktop Display Manager.
nov. 22 06:02:57 fanfan-VR630 systemd[1]: sddm.service: Main process exited, code=killed, status=11/SEGV
nov. 22 06:02:57 fanfan-VR630 systemd[1]: sddm.service: Unit entered failed state.
nov. 22 06:02:57 fanfan-VR630 systemd[1]: sddm.service: Triggering OnFailure= dependencies.
nov. 22 06:02:57 fanfan-VR630 systemd[1]: sddm.service: Failed with result 'signal'.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Network Manager Wait Online.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Reached target Network is Online.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started crash report submission daemon.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Starting LSB: Start NTP daemon...
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Daily apt download activities.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Daily apt upgrade and clean activities.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Reached target Timers.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Starting TeamViewer remote control daemon...
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Starting /etc/rc.local Compatibility...
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Starting LSB: disk temperature monitoring daemon...
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started /etc/rc.local Compatibility.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: sddm.service: Service hold-off time over, scheduling restart.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Stopped Simple Desktop Display Manager.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Starting Detect the available GPUs and deal with any system changes...
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Getty on tty1.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Reached target Login Prompts.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Starting Terminate Plymouth Boot Screen...
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started LSB: disk temperature monitoring daemon.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Received SIGRTMIN+21 from PID 350 (plymouthd).
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Terminate Plymouth Boot Screen.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: teamviewerd.service: PID file /var/run/teamviewerd.pid not readable (yet?) after start: No such file or directory
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started LSB: Start NTP daemon.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Reached target Multi-User System.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started TLP system startup/shutdown.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Detect the available GPUs and deal with any system changes.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started TeamViewer remote control daemon.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Starting Simple Desktop Display Manager...
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Simple Desktop Display Manager.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Reached target Graphical Interface.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Starting Update UTMP about System Runlevel Changes...
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Stop ureadahead data collection 45s after completed startup.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Started Update UTMP about System Runlevel Changes.
nov. 22 06:02:58 fanfan-VR630 systemd[1]: Startup finished in 7.698s (kernel) + 22.541s (userspace) = 30.239s.
nov. 22 06:03:01 fanfan-VR630 systemd[1]: Created slice User Slice of sddm.
nov. 22 06:03:01 fanfan-VR630 systemd[1]: Starting User Manager for UID 122...
nov. 22 06:03:01 fanfan-VR630 systemd[1416]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
nov. 22 06:03:01 fanfan-VR630 systemd[1]: Started Session 1 of user sddm.
nov. 22 06:03:01 fanfan-VR630 systemd-logind[786]: New session 1 of user sddm.
nov. 22 06:03:02 fanfan-VR630 systemd[1416]: Reached target Timers.
nov. 22 06:03:02 fanfan-VR630 systemd[1416]: Reached target Paths.
nov. 22 06:03:02 fanfan-VR630 systemd[1416]: Reached target Sockets.
nov. 22 06:03:02 fanfan-VR630 systemd[1416]: Reached target Basic System.
nov. 22 06:03:02 fanfan-VR630 systemd[1416]: Reached target Default.
nov. 22 06:03:02 fanfan-VR630 systemd[1416]: Startup finished in 86ms.
nov. 22 06:03:02 fanfan-VR630 systemd[1]: Started User Manager for UID 122.
nov. 22 06:03:02 fanfan-VR630 sddm-helper[1409]: pam_systemd(sddm-greeter:session): Cannot create session: Already running in a session
nov. 22 06:03:06 fanfan-VR630 systemd[1]: Time has been changed
nov. 22 06:03:06 fanfan-VR630 systemd[1416]: Time has been changed
nov. 22 06:03:07 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
nov. 22 06:03:07 fanfan-VR630 systemd[1]: Starting Disk Manager...
nov. 22 06:03:07 fanfan-VR630 systemd[1]: Started Disk Manager.
nov. 22 06:03:07 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
nov. 22 06:03:07 fanfan-VR630 systemd[1]: Starting Daemon for power management...
nov. 22 06:03:08 fanfan-VR630 systemd[1]: Started Daemon for power management.
nov. 22 06:03:44 fanfan-VR630 systemd[1]: Starting Stop ureadahead data collection...
nov. 22 06:03:44 fanfan-VR630 systemd[1]: Stopped Read required files in advance.
nov. 22 06:03:44 fanfan-VR630 systemd[1]: Started Stop ureadahead data collection.
nov. 22 06:04:20 fanfan-VR630 systemd[1]: Created slice User Slice of fanfan.
nov. 22 06:04:20 fanfan-VR630 systemd[1]: Starting User Manager for UID 1000...
nov. 22 06:04:20 fanfan-VR630 systemd[2041]: pam_unix(systemd-user:session): session opened for user fanfan by (uid=0)
nov. 22 06:04:20 fanfan-VR630 systemd-logind[786]: New session 2 of user fanfan.
nov. 22 06:04:20 fanfan-VR630 systemd[1]: Started Session 2 of user fanfan.
nov. 22 06:04:20 fanfan-VR630 systemd[2041]: Reached target Timers.
nov. 22 06:04:20 fanfan-VR630 systemd[2041]: Reached target Paths.
nov. 22 06:04:20 fanfan-VR630 systemd[2041]: Reached target Sockets.
nov. 22 06:04:20 fanfan-VR630 systemd[2041]: Reached target Basic System.
nov. 22 06:04:20 fanfan-VR630 systemd[2041]: Reached target Default.
nov. 22 06:04:20 fanfan-VR630 systemd[2041]: Startup finished in 67ms.
nov. 22 06:04:20 fanfan-VR630 systemd[1]: Started User Manager for UID 1000.
nov. 22 06:04:20 fanfan-VR630 sddm-helper[2040]: pam_systemd(sddm:session): Cannot create session: Already running in a session
nov. 22 06:04:28 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
nov. 22 06:04:28 fanfan-VR630 systemd[1]: Starting RealtimeKit Scheduling Policy Service...
nov. 22 06:04:28 fanfan-VR630 systemd[1]: Started RealtimeKit Scheduling Policy Service.
nov. 22 06:04:41 fanfan-VR630 pkexec[2421]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
nov. 22 06:04:41 fanfan-VR630 pkexec[2451]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
nov. 22 06:04:43 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
nov. 22 06:04:45 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
nov. 22 06:04:45 fanfan-VR630 systemd[1]: Starting Hostname Service...
nov. 22 06:04:45 fanfan-VR630 systemd[1]: Started Hostname Service.
nov. 22 06:04:48 fanfan-VR630 pkexec[2534]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
nov. 22 06:04:57 fanfan-VR630 pkexec[2603]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
nov. 22 06:05:08 fanfan-VR630 dbus[782]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
nov. 22 06:12:54 fanfan-VR630 pkexec[3048]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
nov. 22 06:15:00 fanfan-VR630 pkexec[3079]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
nov. 22 06:17:33 fanfan-VR630 systemd[1]: Starting Cleanup of Temporary Directories...
nov. 22 06:17:33 fanfan-VR630 systemd-tmpfiles[3169]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
nov. 22 06:17:33 fanfan-VR630 systemd[1]: Started Cleanup of Temporary Directories.
fanfan@fanfan-VR630:~$

Aussi, je viens de faire l'essai sur mon netbook (mate 16.04 aussi) : J'ai installé sddm comme indiqué au post #2 : pas de reboot, je le fais à la main ; au redémarrage je me retrouve logiquement avec sddm.
Je tente alors de faire l'action inverse (post #7) et ça me fait pareil que sur le portable MSI de mon fils...
écran noir mais à la place du curseur qui clignote, j'ai une demande de login ; ensuite sudo reboot etc ; sddm est toujours là...

A noter que lors de l'installation de ce foutu sddm, à un moment il est demandé de faire le choix entre lightdm et sddm ; pour ma part il me semble avoir choisi sddm... (ça me paraissait logique... mais encore une fois, je n'y connais rien et je ne sais pas ce que ça induit...?)

kersaweol

Je me suis dit qu'il fallait peut-être appliquer les lignes de commande (post #7) les unes après les autres (plutôt qu'en bloc) :
Ligne 1

sudo systemctl stop sddm.service

écran noir, curseur clignotant --> Ctrl+Alt+F1 reboot (comme déjà dit)
Ligne 2

sudo systemctl disable sddm.service

Ça n'empêche pas d'utiliser un autre service, mais lequel ?
Ligne 3

systemctl status gdm.service

Pas gdm en tout cas puisqu'il ne le trouve pas...
Ligne4

sudo systemctl start gdm.service

Pas de gdm...

J'ai fait un redémarrage pour voir... Eh bien me voilà avec un écran noir avec le curseur clignotant ; Ctrl+Alt+F1 reboot : écran noir...
Tout compte fait ça me semble logique puisque sddm a été désactivé et que gdm est introuvable...

D'après ce que j'ai lu gdm n'existe plus depuis 2011... ? Remplacé par lightdm ?

Skubu

GDM, SDDM, LightDM, tout cela sont des gestionnaires de session. Un seul doit être activé mais cela n'empêche pas de tous les installer pour les tester et faire son choix. GDM est toujours sur ton système. Où as-tu lu qu'il n'existe plus ?

Si tu as tout copié le bloc, effectivement, toutes les instructions demandées n'ont pas été prises en compte.

Fais Ctrl+Alt+F1 et réessaie:

$ sudo systemctl disable sddm.service

$ systemctl status sddm.service

Vérifie que tu as

...
Active: inactive (dead)

Si ce n'est pas le cas, systemd donnera un message d'erreur.

$ sudo systemctl enable gdm.service

et ici l'inverse

...
Active: active...

Idem, erreur ou pas ?

Puis si tout est correct

$ sudo systemctl start gdm.service

maxire

Salut,

En principe le gestionnaire de sessions par défaut utilisé par MATE sous Ubuntu est Lightdm, gdm ou plutôt gdm3 n'est pas installé bien que disponible dans les dépôts de la 16.04.

Pour activer le pavé numérique sous Lightdm mettre:


[Seat:*]
greeter-setup-script=/usr/bin/numlockx on

dans /etc/lightdm.conf et puis c'est tout!

Et non mate n'a rien forké du tout en ce qui concerne gdm, c'est Mint qui a forké gdm en MDM et ce n'est pas une réussite.

kersaweol

Alors donc :

phil@N150:~$  sudo systemctl disable sddm.service
[sudo] Mot de passe de phil : 
Synchronizing state of sddm.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install disable sddm
insserv: warning: current start runlevel(s) (empty) of script `sddm' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `sddm' overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `sddm' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `sddm' overrides LSB defaults (0 1 6).
phil@N150:~$

phil@N150:~$ systemctl status sddm.service
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/lib/systemd/system/sddm.service; static; vendor preset: enab
   Active: active (running) since mer. 2017-11-22 18:35:30 CET; 14min ago
     Docs: man:sddm(1)
           man:sddm.conf(5)
 Main PID: 857 (sddm)
   CGroup: /system.slice/sddm.service
           ├─857 /usr/bin/sddm
           └─881 /usr/lib/xorg/Xorg -nolisten tcp -auth /var/run/sddm/{4ff7e25f-

nov. 22 18:35:52 N150 sddm-helper[1129]: [PAM] Authenticating...
nov. 22 18:35:52 N150 sddm-helper[1129]: [PAM] Preparing to converse...
nov. 22 18:35:52 N150 sddm-helper[1129]: [PAM] Conversation with 1 messages
nov. 22 18:35:52 N150 sddm-helper[1129]: pam_kwallet5(sddm:auth): (null): pam_sm
nov. 22 18:35:57 N150 sddm-helper[1129]: [PAM] returning.
nov. 22 18:35:57 N150 sddm[857]: Authenticated successfully
nov. 22 18:35:57 N150 sddm-helper[1129]: pam_kwallet5(sddm:setcred): pam_kwallet
nov. 22 18:35:57 N150 sddm[857]: Auth: sddm-helper exited successfully
nov. 22 18:35:57 N150 sddm[857]: Greeter stopped.
nov. 22 18:35:57 N150 sddm[857]: Session started
lines 1-20/20 (END)

après (END) il y a un curseur sui clignote mais rien ne se passe
donc si j'ai bien compris, j'ai active : active et ce n'est pas bon...

phil@N150:~$ sudo systemctl enable gdm.service
[sudo] Mot de passe de phil : 
Failed to execute operation: No such file or directory
phil@N150:~$

comme déjà dit : pas de service gdm

Vu que rien n'est correct, je ne vais pas plus loin, n'est-ce pas ?

Skubu

Merci maxire pour ces précisions.

La cohabitation entre SysV init et systemd semble compliqué la tâche... Quelle idée !
installes tree

sudo apt-get install tree

et donne les retours de

tree /etc/systemd

tree /etc/init.d/

kersaweol

Skubu a écritLa cohabitation entre SysV init et systemd semble compliqué la tâche... Quelle idée !

Le système est tout fraîchement installé et je n'ai rien installé de ce que je ne connais pas, mis à part ce sddm afin de résoudre le problème d'activation du pavé numérique...

Rappel, j'avais aussi installé ce sddm sur mon netbook (phil) afin de reproduire la situation rencontrée sur l'ordi de mon fils (fanfan), afin de travailler sur la question plus confortablement (je n'ai pas en permanence l'ordi de mon fils avec moi) ; Cela fait exactement pareil...

@ maxire : Avant de poster, comme expliqué dans le post initial, j'avais consulté la doc numlockx et au vu des recommandations faites pour chaque variante d'ubuntu et n'ayant rien trouvé concernant mate, j'ai appliqué ce qui était dit "pour toutes versions"...

Je pense bien appliquer la recommandation que tu me suggères (pour ubuntu) quand je serai débarrassé de ce pot de colle de sddm...

kersaweol

Du nouveau ! Ouf ! J'ai trouvé la solution pour me débarrasser de ce sddm !

Ctrl+Alt+F1
sudo dpkg-reconfigure lightdm
une fenêtre s'affiche pour choisir entre sddm et lightdm --> choix lightdm et voilà !

Ensuite, application de la doc numlockx (section ubuntu après la 14.04) = conseil de maxire : et zou ça roule !

La prochaine fois, fors de cette expérience, je n'appliquerai la doc qu'après avoir posté sur le forum...

Skubu

Tant mieux pour toi.

Mais reste toujours des interrogations:
- Qui a installé lightdm ?
- Pourquoi les devs ubuntu ont-ils eu besoin de garder sysV init et systemd ?
- lightdm est-il plus fluide que sddm ?

Page suivante »