Problèmes et questions concernant le noyau et le support matériel.
Répondre

Failed to start light display manager

#1Messageil y a 3 ans

bonjour,
comment résoudre ce souci,Failed to start light display manager,j ai eu ça au démarrage pc ce matin,ca a fini par fonctionné après plusieurs tentative.
je tourne avec les pilotes propriétaire,le pilote libre crach le pc.mon installation es bien a jour ses une installation de hier.
bonne journée.

Failed to start light display manager

#2Messageil y a 3 ans

bonjour

peux tu nous fournir

inxi -Fza
sudo mhwd -li

Failed to start light display manager

#3Messageil y a 3 ans

voila

inxi -Fza
System:
  Kernel: 5.10.15-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  root=UUID=f4e5a923-3b9e-461a-8c18-a6fa13c9a50f rw quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: ASRock model: N68C-S serial: <filter> 
  BIOS: American Megatrends v: P1.30 date: 06/22/2010 
CPU:
  Info: Quad Core model: AMD Phenom 9500 bits: 64 type: MCP arch: K10 
  family: 10 (16) model-id: 2 stepping: 2 microcode: 1000095 L2 cache: 2 MiB 
  flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 17689 
  Speed: 1100 MHz min/max: 1100/2200 MHz Core speeds (MHz): 1: 1100 2: 2200 
  3: 1100 4: 1100 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass status: Not affected 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 
  mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GF108 [GeForce GT 630] vendor: Micro-Star MSI 
  driver: nvidia v: 390.141 alternate: nouveau,nvidia_drm bus ID: 02:00.0 
  chip ID: 10de:0f00 class ID: 0300 
  Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia display ID: :0.0 
  screens: 1 
  Screen-1: 0 s-res: 1680x1050 s-dpi: 90 s-size: 474x293mm (18.7x11.5") 
  s-diag: 557mm (21.9") 
  Monitor-1: DVI-I-1 res: 1680x1050 hz: 60 dpi: 90 
  size: 474x296mm (18.7x11.7") diag: 559mm (22") 
  OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.4 
  compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: NVIDIA MCP61 High Definition Audio vendor: ASRock 
  driver: snd_hda_intel v: kernel bus ID: 00:05.0 chip ID: 10de:03f0 
  class ID: 0403 
  Device-2: NVIDIA GF108 High Definition Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 02:00.1 chip ID: 10de:0bea 
  class ID: 0403 
  Sound Server: ALSA v: k5.10.15-1-MANJARO 
Network:
  Device-1: NVIDIA MCP61 Ethernet vendor: ASRock 939NF6G-VSTA Board 
  type: network bridge driver: forcedeth v: kernel port: d480 
  bus ID: 00:07.0 chip ID: 10de:03ef class ID: 0680 
  IF: enp0s7 state: down mac: <filter> 
  Device-2: Ralink RT2561/RT61 rev B 802.11g 
  vendor: D-Link System AirPlus G DWL-G510 Wireless driver: rt61pci v: 2.3.0 
  port: c000 bus ID: 01:08.0 chip ID: 1814:0302 class ID: 0280 
  IF: wlp1s8 state: up mac: <filter> 
Drives:
  Local Storage: total: 2.11 TiB used: 587.57 GiB (27.2%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital 
  model: WD20EZRX-00D8PB0 size: 1.82 TiB block size: physical: 4096 B 
  logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 0A80 scheme: MBR 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3320311CS 
  size: 298.09 GiB block size: physical: 512 B logical: 512 B 
  speed: 3.0 Gb/s rotation: 5900 rpm serial: <filter> rev: CA12 scheme: MBR 
Partition:
  ID-1: / raw size: 298.09 GiB size: 292.41 GiB (98.09%) 
  used: 17.84 GiB (6.1%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 
Swap:
  Alert: No Swap data was found. 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Info:
  Processes: 220 Uptime: 4h 17m wakeups: 1580 Memory: 3.84 GiB 
  used: 1.68 GiB (43.7%) Init: systemd v: 247 Compilers: gcc: 10.2.0 
  Packages: 1306 pacman: 1289 lib: 415 rpm: 0 flatpak: 10 snap: 7 
  Shell: Bash v: 5.1.0 running in: xfce4-terminal inxi: 3.3.01 
et

> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
    video-nvidia-390xx            2020.11.30               false            PCI


Warning: No installed USB configs!
Les balises '' sont réservées pour les citations
administration/modération

Failed to start light display manager

#4Messageil y a 3 ans

et une nouveauté
l l excursion du processus fil xfce session logout a échoué
mais quel ,es le souci

Failed to start light display manager

#5Messageil y a 3 ans

il faut voir
-dans les log :
sudo journalctl -b0
sudo systemctl status lightdm.service
sudo systemctl status lightdm-greeter.service

Failed to start light display manager

#6Messageil y a 3 ans

donc sudo journalctl -b0

-- Journal begins at Tue 2021-02-09 21:22:32 CET, ends at Sat 2021-02-13 11:54:43 CET. --
fév 13 11:51:16 asocial-tobefilledbyoem kernel: Linux version 5.10.15-1-MANJARO (builduser@LEGION) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36) #1 SMP PREEMPT Wed >
fév 13 11:51:16 asocial-tobefilledbyoem kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 root=UUID=f4e5a923-3b9e-461a-8c18-a6fa13c9a50f rw quiet apparmor=1>
fév 13 11:51:16 asocial-tobefilledbyoem kernel: x86/fpu: x87 FPU will use FXSAVE
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-provided physical RAM map:
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x00000000000e7000-0x00000000000fffff] reserved
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000effaffff] usable
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x00000000effb0000-0x00000000effbffff] ACPI data
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x00000000effc0000-0x00000000effeffff] ACPI NVS
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x00000000efff0000-0x00000000efffffff] reserved
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
fév 13 11:51:16 asocial-tobefilledbyoem kernel: BIOS-e820: [mem 0x0000000100000000-0x000000010fffffff] usable
fév 13 11:51:16 asocial-tobefilledbyoem kernel: NX (Execute Disable) protection: active
fév 13 11:51:16 asocial-tobefilledbyoem kernel: SMBIOS 2.4 present.
fév 13 11:51:16 asocial-tobefilledbyoem kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./N68C-S, BIOS P1.30 06/22/2010
fév 13 11:51:16 asocial-tobefilledbyoem kernel: tsc: Fast TSC calibration using PIT
fév 13 11:51:16 asocial-tobefilledbyoem kernel: tsc: Detected 2210.121 MHz processor
fév 13 11:51:16 asocial-tobefilledbyoem kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
fév 13 11:51:16 asocial-tobefilledbyoem kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
fév 13 11:51:16 asocial-tobefilledbyoem kernel: last_pfn = 0x110000 max_arch_pfn = 0x400000000
fév 13 11:51:16 asocial-tobefilledbyoem kernel: MTRR default type: uncachable
fév 13 11:51:16 asocial-tobefilledbyoem kernel: MTRR fixed ranges enabled:
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   00000-9FFFF write-back
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   A0000-EFFFF uncachable
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   F0000-FFFFF write-protect
fév 13 11:51:16 asocial-tobefilledbyoem kernel: MTRR variable ranges enabled:
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   0 base 000000000000 mask FFFF80000000 write-back
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   1 base 000080000000 mask FFFFC0000000 write-back
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   2 base 0000C0000000 mask FFFFE0000000 write-back
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   3 base 0000E0000000 mask FFFFF0000000 write-back
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   4 disabled
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   5 disabled
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   6 disabled
fév 13 11:51:16 asocial-tobefilledbyoem kernel:   7 disabled
fév 13 11:51:16 asocial-tobefilledbyoem kernel: TOM2: 0000000110000000 aka 4352M
fév 13 11:51:16 asocial-tobefilledbyoem kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
fév 13 11:51:16 asocial-tobefilledbyoem kernel: e820: update [mem 0xf0000000-0xffffffff] usable ==> reserved
fév 13 11:51:16 asocial-tobefilledbyoem kernel: last_pfn = 0xeffb0 max_arch_pfn = 0x400000000
fév 13 11:51:16 asocial-tobefilledbyoem kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f]
fév 13 11:51:16 asocial-tobefilledbyoem kernel: check: Scanning 1 areas for low memory corruption
fév 13 11:51:16 asocial-tobefilledbyoem kernel: Using GB pages for direct mapping
fév 13 11:51:16 asocial-tobefilledbyoem kernel: RAMDISK: [mem 0x371ef000-0x378eefff]
fév 13 11:51:16 asocial-tobefilledbyoem kernel: ACPI: Early table checksum verification disabled
fév 13 11:51:16 asocial-tobefilledbyoem kernel: ACPI: RSDP 0x00000000000FB580 000014 (v00 ACPIAM)
fév 13 11:51:16 asocial-tobefilledbyoem kernel: ACPI: RSDT 0x00000000EFFB0000 000040 (v01 A_M_I  OEMRSDT  06001022 MSFT 00000097)
sudo systemctl status lightdm.service

● lightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor p>
     Active: active (running) since Sat 2021-02-13 11:51:43 CET; 4min 9s ago
       Docs: man:lightdm(1)
   Main PID: 564 (lightdm)
      Tasks: 16 (limit: 4702)
     Memory: 79.7M
     CGroup: /system.slice/lightdm.service
             ├─564 /usr/bin/lightdm
             └─597 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nol>

fév 13 11:51:37 asocial-tobefilledbyoem systemd[1]: Starting Light Display Mana>
fév 13 11:51:43 asocial-tobefilledbyoem systemd[1]: Started Light Display Manag>
fév 13 11:51:50 asocial-tobefilledbyoem lightdm[783]: pam_succeed_if(lightdm-au>
fév 13 11:51:50 asocial-tobefilledbyoem lightdm[783]: gkr-pam: no password is a>
fév 13 11:51:50 asocial-tobefilledbyoem lightdm[783]: pam_systemd_home(lightdm->
fév 13 11:51:50 asocial-tobefilledbyoem lightdm[783]: pam_unix(lightdm-autologi>
lines 1-17/17 (END)...skipping...
● lightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
     Active: active (running) since Sat 2021-02-13 11:51:43 CET; 4min 9s ago
       Docs: man:lightdm(1)
   Main PID: 564 (lightdm)
      Tasks: 16 (limit: 4702)
     Memory: 79.7M
     CGroup: /system.slice/lightdm.service
             ├─564 /usr/bin/lightdm
             └─597 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

fév 13 11:51:37 asocial-tobefilledbyoem systemd[1]: Starting Light Display Manager...
fév 13 11:51:43 asocial-tobefilledbyoem systemd[1]: Started Light Display Manager.
fév 13 11:51:50 asocial-tobefilledbyoem lightdm[783]: pam_succeed_if(lightdm-autologin:auth): requirement "user ingroup autologin" was met by user "asocial"
fév 13 11:51:50 asocial-tobefilledbyoem lightdm[783]: gkr-pam: no password is available for user
fév 13 11:51:50 asocial-tobefilledbyoem lightdm[783]: pam_systemd_home(lightdm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.se>
fév 13 11:51:50 asocial-tobefilledbyoem lightdm[783]: pam_unix(lightdm-autologin:session): session opened for user asocial(uid=1000) by (uid=0)

Unit lightdm-greeter.service could not be found.
Il t'as déjà été demandé de n'utiliser les balises quote uniquement pour les citations de personne.
Pour les retours de commandes, il faut utiliser les balise code </>.
Fait
administration/modération

Failed to start light display manager

#7Messageil y a 3 ans

Bonjour,
j'ai eu le même problème et je l'ai résolu en le désactivant et réactivant dans systemd

sudo systemctl disable lightdm
sudo systemctl enable lightdm
sudo systemctl start lightdm
Depuis ça fonctionne bien.
Après pourquoi comment je sais pas !!!

ça me le faisait avec le kernel 5.9, 5.10 et le 5.11rc
avec le 5.4 je n'avais pas ce problème
Répondre