Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] Stuck at boot logo - lightdm failed to start

Off-Topic discussions about science, technology, and non Debian specific topics.
Post Reply
Message
Author
Gran061
Posts: 8
Joined: 2020-01-15 12:17

[SOLVED] Stuck at boot logo - lightdm failed to start

#1 Post by Gran061 »

Good day

Since the Deepin forum does not help anyone much, I am posting here hoping that it's allowed and that I can get assistance, since Deepin in Debian 9 based.

Yesterday I installed some packages to try and get my iPhone to connect via iFuse, which ended up failing. I then removed this said packages, and with that, I also removed the light display manager (lightdm) package by accident.

Now when I boot up, I am stuck at the Deepin logo. I tried the following:

1. Tried accessing recovery mode
- This failed because I now get an error saying something about failed to access console root is locked. Which then tries to boot back into the UI.

2. I tried 'Ctrl + Alt + F2' too, and this did not work either since the system does not boot.

Please see image attached for the boot error. I am stuck right now and I have no idea what else I am supposed to do right now. PLEASE help I am in a huge need!

Image Link: https://nimb.ws/l3YLVW

----------------------------

Edit 1:

I sat another hour with this but was unable to resolve it. This was the new steps I took to try to resolve my issue:

1. Boot from Deepin LiveUSB
2. Mounted my file system partition and went into chroot
2.1 I ran the following commands:
- mkdir /mnt/hdd && mount /dev/sdb1 /mnt/hdd
- mount -t proc none /mnt/hdd/proc
- mount -o bind /dev /mnt/hdd/dev
- mount -o binf /sys /mnt/hdd/sys
- cp /etc/resolv.conf /mnt/hdd/etc/resolv.conf (To have internet access)
- chroot /mnt/hdd /bin/bash
3. Ran 'apt install lightdm' - and it told me that I already have the latest version installed (Yes, this means it was never missing if I understand correctly).
4. Ran 'apt remove --purge lightdm'
5. Ran 'apt install lightdm' - got an error about /var/lib/lightdm not reachable - but it completed I believed, the install
6. Since I removed a bunch of packages during the iFuse trial, I decided to re-install them all again.

Rebooted, and the problem still persisted. Sighhh I am having a mini panic attack because it's my daily drive OS and now I am screwed. I really hope there's someone that can assist, please.
Last edited by Gran061 on 2020-01-16 07:16, edited 1 time in total.

Chrisdb
Posts: 279
Joined: 2018-04-10 07:16

Re: Stuck at boot logo - lightdm failed to start

#2 Post by Chrisdb »

Gran061 wrote:Good day

Since the Deepin forum does not help anyone much, I am posting here hoping that it's allowed and that I can get assistance, since Deepin in Debian 9 based.

Yesterday I installed some packages to try and get my iPhone to connect via iFuse, which ended up failing. I then removed this said packages, and with that, I also removed the light display manager (lightdm) package by accident.

Now when I boot up, I am stuck at the Deepin logo. I tried the following:

1. Tried accessing recovery mode
- This failed because I now get an error saying something about failed to access console root is locked. Which then tries to boot back into the UI.

2. I tried 'Ctrl + Alt + F2' too, and this did not work either since the system does not boot.

Please see image attached for the boot error. I am stuck right now and I have no idea what else I am supposed to do right now. PLEASE help I am in a huge need!

Image Link: https://nimb.ws/l3YLVW

----------------------------

Edit 1:

I sat another hour with this but was unable to resolve it. This was the new steps I took to try to resolve my issue:

1. Boot from Deepin LiveUSB
2. Mounted my file system partition and went into chroot
2.1 I ran the following commands:
- mkdir /mnt/hdd && mount /dev/sdb1 /mnt/hdd
- mount -t proc none /mnt/hdd/proc
- mount -o bind /dev /mnt/hdd/dev
- mount -o binf /sys /mnt/hdd/sys
- cp /etc/resolv.conf /mnt/hdd/etc/resolv.conf (To have internet access)
- chroot /mnt/hdd /bin/bash
3. Ran 'apt install lightdm' - and it told me that I already have the latest version installed (Yes, this means it was never missing if I understand correctly).
4. Ran 'apt remove --purge lightdm'
5. Ran 'apt install lightdm' - got an error about /var/lib/lightdm not reachable - but it completed I believed, the install
6. Since I removed a bunch of packages during the iFuse trial, I decided to re-install them all again.

Rebooted, and the problem still persisted. Sighhh I am having a mini panic attack because it's my daily drive OS and now I am screwed. I really hope there's someone that can assist, please.
Although I'm not familiar with Deepin, I will try to help.

From the errors it seems that LightDM is not enabled, so please try:

Code: Select all

sudo systemctl enable lightdm.service
sudo systemctl start lightdm.service
If this still doesn't work, post the results of the following:

Code: Select all

sudo systemctl status lightdm.service

Gran061
Posts: 8
Joined: 2020-01-15 12:17

Re: Stuck at boot logo - lightdm failed to start

#3 Post by Gran061 »

Chrisdb wrote:
Although I'm not familiar with Deepin, I will try to help.

From the errors it seems that LightDM is not enabled, so please try:

Code: Select all

sudo systemctl enable lightdm.service
sudo systemctl start lightdm.service
If this still doesn't work, post the results of the following:

Code: Select all

sudo systemctl status lightdm.service
Hi Chrisdb

Thank you for getting back to me so quickly. Your solution assumes that I can boot into the OS to run those commands when I cannot. Can you tell me where I am supposed to run these commands, please? It does not boot me into the OS at all and just remains stuck on the boot logo.

Chrisdb
Posts: 279
Joined: 2018-04-10 07:16

Re: Stuck at boot logo - lightdm failed to start

#4 Post by Chrisdb »

Gran061 wrote:
Chrisdb wrote:
Although I'm not familiar with Deepin, I will try to help.

From the errors it seems that LightDM is not enabled, so please try:

Code: Select all

sudo systemctl enable lightdm.service
sudo systemctl start lightdm.service
If this still doesn't work, post the results of the following:

Code: Select all

sudo systemctl status lightdm.service
Hi Chrisdb

Thank you for getting back to me so quickly. Your solution assumes that I can boot into the OS to run those commands when I cannot. Can you tell me where I am supposed to run these commands, please? It does not boot me into the OS at all and just remains stuck on the boot logo.
If you're not able to run the commands, boot with your LiveUSB and launch the commands in chroot.

I just noticed the last error from your screenshot, can you run the following:

Code: Select all

sudo apt-get remove plymouth
it could be plymouth is having issues with your DM.

Gran061
Posts: 8
Joined: 2020-01-15 12:17

Re: Stuck at boot logo - lightdm failed to start

#5 Post by Gran061 »

Chrisdb wrote:
Gran061 wrote:
Chrisdb wrote:
Although I'm not familiar with Deepin, I will try to help.

From the errors it seems that LightDM is not enabled, so please try:

Code: Select all

sudo systemctl enable lightdm.service
sudo systemctl start lightdm.service
If this still doesn't work, post the results of the following:

Code: Select all

sudo systemctl status lightdm.service
Hi Chrisdb

Thank you for getting back to me so quickly. Your solution assumes that I can boot into the OS to run those commands when I cannot. Can you tell me where I am supposed to run these commands, please? It does not boot me into the OS at all and just remains stuck on the boot logo.
If you're not able to run the commands, boot with your LiveUSB and launch the commands in chroot.

I just noticed the last error from your screenshot, can you run the following:

Code: Select all

sudo apt-get remove plymouth
it could be plymouth is having issues with your DM.
Any of those commands I run in chroot I get this error:

sudo: unable to resolve host deepin
Running in chroot, ignoring request.
root@deepin:/#

I ran plymouth remove command you asked and now I get this:

The following packages will be REMOVED:
lightdm plymouth plymouth-theme-deepin-logo
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 9,538 kB disk space will be freed.

Should I proceed?

Chrisdb
Posts: 279
Joined: 2018-04-10 07:16

Re: Stuck at boot logo - lightdm failed to start

#6 Post by Chrisdb »

yes and then reinstall lightdm

Gran061
Posts: 8
Joined: 2020-01-15 12:17

Re: Stuck at boot logo - lightdm failed to start

#7 Post by Gran061 »

Chrisdb wrote:yes and then reinstall lightdm
Please see the results:

Code: Select all

root@deepin:/# sudo apt-get install lightdm
sudo: unable to resolve host deepin
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  plymouth
Suggested packages:
  upower desktop-base plymouth-themes
The following NEW packages will be installed:
  lightdm plymouth
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 282 kB of archives.
After this operation, 1,287 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://packages.deepin.com/deepin lion/main amd64 plymouth amd64 0.9.2-4 [118 kB]
Get:2 http://packages.deepin.com/deepin lion/main amd64 lightdm amd64 1.21.6-1 [165 kB]
Fetched 282 kB in 16s (17.3 kB/s)
Preconfiguring packages ...
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Selecting previously unselected package plymouth.
(Reading database ... 220725 files and directories currently installed.)
Preparing to unpack .../plymouth_0.9.2-4_amd64.deb ...
Unpacking plymouth (0.9.2-4) ...
Selecting previously unselected package lightdm.
Preparing to unpack .../lightdm_1.21.6-1_amd64.deb ...
Unpacking lightdm (1.21.6-1) ...
Processing triggers for deepin-desktop-base (2019.07.10-1+comsta) ...
postinst called with unknown argument `triggered'
Setting up plymouth (0.9.2-4) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Processing triggers for systemd (232-25+deb9u6) ...
Setting up lightdm (1.21.6-1) ...
Running in chroot, ignoring request.
[....] Reloading system message bus config...Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
invoke-rc.d: initscript dbus, action "reload" failed.
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for dbus (1.10.26-0+deb9u1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-30deepin-generic
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead.
grep: /proc/swaps: No such file or directory
loadkeys is missing. Please install the 'kbd' package.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.
root@deepin:/# 
I see a lot of errors, which looks worrisome.

Chrisdb
Posts: 279
Joined: 2018-04-10 07:16

Re: Stuck at boot logo - lightdm failed to start

#8 Post by Chrisdb »

Gran061 wrote:
I see a lot of errors, which looks worrisome.
Did you configure the mounts correctly?

Code: Select all

# mount -t proc /proc proc/
# mount --rbind /sys sys/
# mount --rbind /dev dev/
**EDIT
And for the DBUS error:

Code: Select all

mount --bind /var/run/dbus/ mnt/hdd/var/run/dbus/

Gran061
Posts: 8
Joined: 2020-01-15 12:17

Re: Stuck at boot logo - lightdm failed to start

#9 Post by Gran061 »

Chrisdb wrote:
Gran061 wrote:
I see a lot of errors, which looks worrisome.
Did you configure the mounts correctly?

Code: Select all

# mount -t proc /proc proc/
# mount --rbind /sys sys/
# mount --rbind /dev dev/
**EDIT
And for the DBUS error:

Code: Select all

mount --bind /var/run/dbus/ mnt/hdd/var/run/dbus/
Okay I am going to re-do the mount process with your guide and then re-do the steps too. Give me a few mins

Gran061
Posts: 8
Joined: 2020-01-15 12:17

Re: Stuck at boot logo - lightdm failed to start

#10 Post by Gran061 »

So here is where I ran everything from scratched and followed your instructions, please look it through. I am going to reboot now and see if it does anything:

Code: Select all

root@deepin:/home/deepin# mkdir /mnt/hdd && mount /dev/sdb1 /mnt/hdd
root@deepin:/home/deepin# mount -t proc /proc /mnt/hdd/proc/
root@deepin:/home/deepin# mount --rbind /sys /mnt/hdd/sys/
root@deepin:/home/deepin# mount --rbind /dev /mnt/hdd/dev/
root@deepin:/home/deepin# mount --bind /var/run/dbus/ /mnt/hdd/var/run/dbus/
root@deepin:/home/deepin# chroot /mnt/hdd /bin/bash 
root@deepin:/# sudo apt-get remove plymouth
sudo: unable to resolve host deepin
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  lightdm plymouth
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 1,287 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 220937 files and directories currently installed.)
Removing lightdm (1.21.6-1) ...
hostname: Name or service not known
Removing plymouth (0.9.2-4) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for deepin-desktop-base (2019.07.10-1+comsta) ...
postinst called with unknown argument `triggered'
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-30deepin-generic
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead.
grep: /proc/swaps: No such file or directory
loadkeys is missing. Please install the 'kbd' package.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.
Processing triggers for man-db (2.7.6.1-2) ...
root@deepin:/# sudo apt-get install lightdm
sudo: unable to resolve host deepin
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  plymouth
Suggested packages:
  upower desktop-base plymouth-themes
The following NEW packages will be installed:
  lightdm plymouth
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/282 kB of archives.
After this operation, 1,287 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Preconfiguring packages ...
Selecting previously unselected package plymouth.
(Reading database ... 220725 files and directories currently installed.)
Preparing to unpack .../plymouth_0.9.2-4_amd64.deb ...
Unpacking plymouth (0.9.2-4) ...
Selecting previously unselected package lightdm.
Preparing to unpack .../lightdm_1.21.6-1_amd64.deb ...
Unpacking lightdm (1.21.6-1) ...
Processing triggers for deepin-desktop-base (2019.07.10-1+comsta) ...
postinst called with unknown argument `triggered'
Setting up plymouth (0.9.2-4) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Processing triggers for systemd (232-25+deb9u6) ...
Setting up lightdm (1.21.6-1) ...
Running in chroot, ignoring request.
[....] Reloading system message bus config...Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
invoke-rc.d: initscript dbus, action "reload" failed.
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for dbus (1.10.26-0+deb9u1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-30deepin-generic
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead.
grep: /proc/swaps: No such file or directory
loadkeys is missing. Please install the 'kbd' package.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.
root@deepin:/# sudo apt-get install plymouth-theme-deepin-logo
sudo: unable to resolve host deepin
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  plymouth-theme-deepin-logo
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,784 kB of archives.
After this operation, 8,250 kB of additional disk space will be used.
Get:1 http://packages.deepin.com/deepin lion/main amd64 plymouth-theme-deepin-logo all 15.10.9-1+comsta [4,784 kB]
Fetched 4,784 kB in 6s (793 kB/s)                                                                                                 
Selecting previously unselected package plymouth-theme-deepin-logo.
(Reading database ... 220938 files and directories currently installed.)
Preparing to unpack .../plymouth-theme-deepin-logo_15.10.9-1+comsta_all.deb ...
Unpacking plymouth-theme-deepin-logo (15.10.9-1+comsta) ...
Setting up plymouth-theme-deepin-logo (15.10.9-1+comsta) ...
/boot/initrd.img-4.14.13 does not exist. Cannot update.
root@deepin:/# 

Gran061
Posts: 8
Joined: 2020-01-15 12:17

Re: Stuck at boot logo - lightdm failed to start

#11 Post by Gran061 »

The solution provided did not work. However, I managed to access recovery mode via unlocking my root account. And I managed to take these screenshots:

- https://nimb.ws/lvUn3G

**EDIT

Some guy on another forum also said I need to try this:

Code: Select all

sudo apt-get install --reinstall dde
From the initial screenshot I sent, he thinks there are components missing or corrupt for DDE

Gran061
Posts: 8
Joined: 2020-01-15 12:17

Re: Stuck at boot logo - lightdm failed to start

#12 Post by Gran061 »

After all the fuss I had all day, the final fix was that I had to run this:

Code: Select all

sudo apt-get install --reinstall dde
I can now successfully boot into my Deepin OS. Thank you so much for your help and assistance.

Post Reply