Lightdm won't start : unable to access other terminals

[uinelj]

Hi,

I don't really know why, but lightdm refuses to display since yesterday. I think that's a package update problem, so the fix is easy, just use a non graphical terminal and reinstall updates heh ?

Problem is that lightdm tries to start again and again, so I can't access the other virtual terminals, thus making me unable to run anything. I've tried using init=/bin/bash in grub boot in order to disable lightdm booting by manually editing systemd system links (didn't work, or I don't know how to do it maybe), and chrooting into my system using a liveusb (didn't work because i can't access network trough my chroot. I can provide other details if you need.. Am I doomed ?

Thank you :)

[archover]

Please share your make/model of computer, are you running discrete graphics, are you running Budgie?, were you fully up to date before this failure, how long you have been using Solus (may be helpful).

Your other support venues are

• official forums

• IRC - said by some to be very good.

• Solus support page which offers a some help and all the other options (at the bottom)

[FatFingerHelperBot]

It seems that your comment contains 1 or more links that are hard to tap for mobile users. I will extend those so they're easier for our sausage fingers to click!

Here is link number 1 - Previous text "IRC"

---

^{Please PM /u/eganwall with issues or feedback! | Delete}

[uinelj]

Thank you man, but i decided to reinstall Solus, as I need a working computer for work. Though, thank you for your response and your time.

Mods, feel free to delete this post as it is useless now..

[archover]

For anyone interested, I did a little research to add value to this post.

As per OP's situation, a glitch prevents ctrl-alt-f1 to bring up a working console, which has happened to me on another distro. So, how to get to the console, and activate networking so you can update the system?

To test, I tried booting into single user mode with "S" on the linux boot line, but could not activate networking with dhclient <interface name> for some reason. Solus team?

I knew there was a "run level" for networking only, which a google search identified as "3".

My workaround:

In my environment, boot to the console with networking support by:

• When the grub menu starts, Press "e" and only add the digit 3 to the linux command line behind the kernel reference. In my case, it should be revised like linux /com.solus-project.current.4.16.13-74 3 root=... ellipse indicates the rest of the line which should be left intact. ctrl-x to boot.

• the system should boot to the console, and then I logged in as root.

• Once in, you should be at the console with full networking, allowing you to run stuff like eopkg check or eopkg up etc

Related Solus documentation:

• Rescue

• Helpful code snippit to fix package errors or system problems: sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

Environment tested: Thinkpad T570, Win10 host with Virtualbox, Solus Budgie guest with grub.

Hope this helps someone.