After Stable Update 2021-09-24 LightDM no longer automatically start

Wrong file.

Please start reading from here as @pheiduck already mentioned

:bowing_man:

I spent a great part of the morning reading that page several times before posting. Sorry but this is all way above my understanding. I stick to startx.

OK, seems like you overlooked something simple:

For example to enable early KMS for the Intel graphics driver:
/etc/mkinitcpio.conf
MODULES=(... i915 ...)

(Emphasis mine…)

:stuck_out_tongue_winking_eye: :grin:

Furthermore also @Aragorn explained to you what you have to do:

But you’ll have to add amd instead of i915:

MODULES=(amd)


However I repeat that in my case this doesn’t help with lightdm.service’s problem.

1 Like

Thank you so much for replying. In a terminal I did sudo pacman -S mkinitcpio and it simply re-installed the file. So it is properly installed somewhere but I do not know where exactly. The second issue is how and where do I add the text MODULES=(amd)? Again, thanks a lot. :slightly_smiling_face:

sudo nano /etc/mkinitcpio.conf

add to the Modules section and save as the above poster suggested.

Thanks. I just spent the last 1/2 hour on DDG and Ytube and found exactly what you are suggesting I should do. And it worked. Thanks to all savvy members who shared their knowledge to help me. Much appreciated.

3 Likes

So, to summarize: editing mkinitcpio, for you, did solved the issue of lightdm which didn’t auto start?

After editing the Modules section of the mkinitcpio.conf file, I regenerate initramfs as follows: sudo mkinitcpio -p linux514 (5.14.x being the current kernel installed). I am still testing the system with several log-outs/reboots/restarts, so far I would say I have had 90% success. Hope this additional info helps.

2 Likes

I have too the same issue since a while. I’ve tried a lot of thinks without any success.
However, I have this issue with since the 5.10. With the 5.14 he seems to be partially resolved i.e sometimes I must use startx for getting my desktop Cinnamon.
And with the 5.4 and 4.19 no worries all works fine.
But when I done an update, I noticed that /usr/bin/grub-probe doesn’t found my system on nvme0n1

:: Exécution des crochets de post-transaction…
( 1/23) Creating system user accounts...
( 2/23) Updating journal message catalog...
( 3/23) Reloading system manager configuration...
( 4/23) Updating udev hardware database...
( 5/23) Applying kernel sysctl settings...
( 6/23) Creating temporary files...
( 7/23) Reloading device manager configuration...
( 8/23) Arming ConditionNeedsUpdate...
( 9/23) Rebuilding certificate stores...
(10/23) Updating module dependencies...
(11/23) Install DKMS modules
==> dkms install --no-depmod -m i2c-piix4-aura -v 5.6.11 -k 5.4.144-1-MANJARO
==> dkms install --no-depmod -m asus-wmi-sensors -v 57.d3b68db -k 5.4.144-1-MANJARO
==> dkms install --no-depmod -m asus-wmi-sensors -v 57.d3b68db -k 5.10.63-1-MANJARO
==> dkms install --no-depmod -m vboxhost -v 6.1.26_OSE -k 5.4.144-1-MANJARO
==> dkms install --no-depmod -m i2c-piix4-aura -v 5.6.11 -k 5.10.63-1-MANJARO
==> dkms install --no-depmod -m vboxhost -v 6.1.26_OSE -k 4.19.206-1-MANJARO
==> dkms install --no-depmod -m vboxhost -v 6.1.26_OSE -k 5.10.63-1-MANJARO
==> dkms install --no-depmod -m i2c-piix4-aura -v 5.6.11 -k 4.19.206-1-MANJARO
Error! Bad return status for module build on kernel: 4.19.206-1-MANJARO (x86_64)
Consult /var/lib/dkms/i2c-piix4-aura/5.6.11/build/make.log for more information.
==> Warning, `dkms install --no-depmod -m i2c-piix4-aura -v 5.6.11 -k 4.19.206-1-MANJARO' returned 10
==> dkms install --no-depmod -m asus-wmi-sensors -v 57.d3b68db -k 4.19.206-1-MANJARO
==> depmod 5.4.144-1-MANJARO
==> depmod 5.10.63-1-MANJARO
==> depmod 4.19.206-1-MANJARO
(12/23) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'default'
  -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64.img
==> Starting build: 4.19.206-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux419.preset: 'fallback'
  -> -k /boot/vmlinuz-4.19-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.19-x86_64-fallback.img -S autodetect
==> Starting build: 4.19.206-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.19-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.63-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: 5.10.63-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: 5.4.144-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: 5.4.144-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> Image generation successful
(13/23) Updating Grub-Bootmenu
Création du fichier de configuration GRUB…
Thème trouvé : /usr/share/grub/themes/manjaro/theme.txt
Image Linux trouvée : /boot/vmlinuz-5.10-x86_64
Image mémoire initiale trouvée : /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Image Linux trouvée : /boot/vmlinuz-5.4-x86_64
Image mémoire initiale trouvée : /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Image Linux trouvée : /boot/vmlinuz-4.19-x86_64
Image mémoire initiale trouvée : /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Attention : le sondeur de systèmes d'exploitation sera exécuté pour détecter d'autres partitions amorçables.
Sa sortie sera utilisée pour détecter les binaires amorçables qu'elles contiennent et créer de nouvelles entrées d'amorçage.
Ajout de l'entrée du menu d'amorçage pour les paramètres du firmware UEFI …
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe : attention : type de périphérique nvme0n1 inconnu.
fait

I have this issue since the update of 24 September 2021; I tried all other kernels without success.

This is a different issue: would be better if you open another discussion in the support section, to get more attention :slight_smile:

Thanks D.Dave for the answer.

Only a difference about the date of this issue, I was thinking that was similar. Let me make the update and see how it will be. Afterwards, I increasingly consider putting KDE. Ah if Cutefish bone was stable, but it is far from it.

Anyway, I’m building myself another pc, I just have left and it will be for next month.

I had the same issue even with logind-check-graphical=true. But I had the config in the wrong section ([Seat:*] instead of [LightDM]). Moving it to the correct section seemed to fix the issue, but it could just be that the error doesn’t always happen.

So we may open up a club :rofl:
I am also affected.(nouveau, lightdm, xfce) But it does hit not every time.

  • One time i updated → no GUI after boot (3 times) :cold_sweat:
  • Rollback → lightdm works 98% (dual seat) :smiley:
  • I start from manjaro-usb without update → OK (but single seat) :smiley:
  • I start from manjaro-usb with update → no GUI (even with single seat) :sob:
    **So the problem must be in the update ??? **

NO !

  • I start from manjaro-usb with update → OK :thinking:
  • Now, when i start from USB, lightdm works 95%. I will have to try the update again.

Update:

SOLVED :sunglasses: see at Loginctl with second seat leads to crash of xorg/lightdm - #13 by andreas85

So yeah,
I have the same issue.
I recently installed Manj. I3 with lightdm and nouveau.
If I have Lightdm disabled my system freezes.
What do I do?
Switch distro?

EDIT:
I checked out endevourOs with the same hardware and lightdm and it worked,
so somewhere something is broken or miscondifuredacross all the diffrent manjaro falvours.

This workaround didn’t solved the issue for me.

@D.Dave did you test a newer ISO to see if the issue is also there?

Hi @philm, I tried with the iso manjaro-xfce-21.1.6-211017-linux513.iso: also there lightdm doesn’t automatically starts.

I assume if you start that ISO in a VM it will start lightdm automatically. So some is special about your hardware. Maybe change to a different display manager ?!?

Last time I tried SDDM and LXDM; currently they both freeze/hangs the system: is like that my system refuse to use any display manager.

The only one that used to work after lightdm issue, was LXDM, but after login it used to reset the mouse cursor to Adwaita (I use “Bibata Amber”), but as I’ve said, now also LXDM doesn’t works.