Failed to start light display manager - lightdm.service

drumcode

I've installed 4.6 Convergence to an SSD from USB (inclusing bootloader, BIOS system/NO UEFI, "erase whole disk" choice, no partitions except for the 1MB FAT partition Solus creates, LTS kernel) and installed some software on it. Then I put the SSD into an older system. That's where the following line and nothing else appears at bootup:

[FAILED] Failed to start lightdm.service - Light Display Manager.

Then I did the following:
Ctrl+Alt+F2 (TTY) to get to the system.
sudo eopkg up - Result: Repositories up to date, no new packages.
sudo eopkg check - Result: all green/OK.
sudo lightdm --test-mode --debug > lightdm_debug_log - Result: visible debug list, but when I cat lightdm_debug_log it's empty (maybe a syntax error by myself?)

What's readable on screen is:

DEBUG: Using VT 7
Seat seat0: Starting local X display on VT 7
XServer 0: Logging to /var/log/lightdm/x-0.log
XServer 0: Writing X Server authority to /run/lightdm/root/:0
XServer 0: Launching X Server
Launching process 888: /usr/lib64/lightdm/xserver-wrapper :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
XServer 0: Waiting for ready signal from X Server :0
Acquired bus name org.freedesktop.DisplayManager
Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
Loading users from org.freedesktop.Accounts
User /org/freedesktop/Accounts/User1000 added
Seat seat0 changes active session to
Process 888 exited with return value 1
XServer 0: Server stopped
Releasing VT 7
XServer 0: Removing X server authority /run/lightdm/root/:0
Seat seat 0: Display server stopped, Stopping session, Session stopped, Stopping display server, no sessions require it, Stopping; greeter display server failed to start, Stopping, Stopped
Required seat has stopped
Stopping display manager
Display manager stopped
Stopping daemon
Exiting with return value 1!<

Then I tested the SSD on another old system (one is an AMD Athlon Dualcore the other an Intel i3-2xxx series, both DDR3 systems) with the exact same error.
Then I put the SSD into my main system again and it worked flawlessly.

The display device connected to both older systems is a CRT monitor. Could that have anything to do with the error?

How do I troubleshoot this further?

Thanks!

PS.: I've read this helpful thread.

BuzzPCSOS

drumcode As a start point it would be good to know what hardware these machines are running. CPU, RAM, Graphics card.
Also have you tried booting the other machines directly from the Solus iso as there may be another fault causing them to fail. You should be able to boot from the iso without a hard drive connected.
Finally what version of Solus are you using? Plasma, Gnome, Budgie or XFCE ?

drumcode

I did a usysconf run -f which went fine (and also removed some old kernel entries) and now it magically works.

ReillyBrogan

drumcode I imagine the graphics hardware was different between the two systems. Usysconf is responsible for running the triggers that copy the right xorg configs into place depending on gpu.

drumcode

BuzzPCSOS
Budgie always.
Booting from the USB thumbdrive is a good idea, I'll keep that in mind should I ever be so unlucky with an installation again. Cheers.

ReillyBrogan
Thanks for the insight. So when implanting a prepared drive into another machine, I'll do a usysconf and update-grub next time right away.

Putting the same drive into another very similar PC with the same CPU type and a discrete GPU leads to 4.6 hanging at "Loading initial ramdisk", and this is after sudo eokpg check (all green) and usysconf run -f (all green), twice.