Mx-23.2 boot failure

[Charlie Brown]

Have you tried what happens if you boot with systemd ? (Select and systemd option on Grub - "Advanced Options" )

(If it wasn't the login screen we could even try what happens with a new user but I think it'll be the same there)

Oh la la:

"MX User Manager" from menu ("Options" tab), you can check what it's set to and if you like set it to autologin for james .

[Charlie Brown]

Remembered one more thing (I was thinking you already did that but searched the previous posts and it seems you didn't) :

Boot with live usb (your snapshot may be) => GParted : right-click on MX partition ( nvme2n1p2 ) : "Check".

[james]

Charlie B: Sorry, I was refreshing the web page, but it incremented to page 9 and just noticed. As for "MX User Manager" from menu ("Options" tab), you can check what it's set to and if you like set it to autologin for james" there is no autologin on the Options tab. BUT when I look at Group Membership tab, the "lightdm" box is NOT CHECKED. Let me know if you want me to put a check in it. OK, gonna try your other two suggestions. Man, I hate Grub. Here goes.

[james]

OK. as for Grub, I do not understand your instructions. I rebooted, and when the splash screen came up, I pressed "e" to get into Grub. There is no GUI, no Advanced Options - it just seems to list about ten lines. So, got out of that, looked at Advanced Options on the splash screen, and there were a bunch of kernels listed to choose from. I did not see a systemd choice. Sorry, I'm probably being thick; if you can give me more of a description....
Then I rebooted with the Snapshot ISO, went to gParted, did a check. The "details" were not very detailed: when I did the check it just said nvme0n1p2 (remember the designations got shuffled, so it's zero now) "All operations competed successfully". And when I rebooted, no change.

[james]

OK, sorry, rebooted again; I don't know how I missed it. In Advanced options where it listed the kernels, there was "systemd" as a choice at the end of some of the lines, so I chose the most recent (which I'm using) and unfortunately, it still did the same things. Sometimes I don't see something that's right in front of me.

[Charlie Brown]

... pressed "e" to get into Grub...

Nope.

... looked at Advanced Options on the splash screen...

Yep.

... a bunch of kernels listed to choose from...

Yep.

... did not see a systemd choice...

Weird.

... Group Membership tab, the "lightdm" box is NOT CHECKED ...

Normal.

... there is no autologin on the Options tab ...

[Charlie Brown]

When I ask myself what I would do: Just try (at least to see) what happens if autologin enabled (though normally I don't prefer this), and if still issues: Copy important files to somewhere and reinstall :)

(Then... when(ever) everything's fine : MX Snapshot and/or Timeshift , both from menu :) )

[james]

Charlie Brown: Again, please accept my apology about looking STRAIGHT AT the kernel list and failing to notice the systemd option at the end of some of the kernels RIGHT IN FRONT OF MY FACE. Well, anyway, went back, found it, tried it, no dice. As for the Options Tab in User Manager, I am pasting in what I see, and I still don't see it. Don't worry about it - I know you are trying to save me some time but having to log each time I reboot in while you are helping me is not too much to ask.

[Charlie Brown]

Oh la la , that's really interesting :)

Let's simply create another user just to test: You can either use that tool to create a new user or simply:

Code: Select all

sudo adduser charlie

Now either reboot (and if needed login manually as charlie) or just logout, then login (as charlie).

In the meantime we never tried what happens when you just do a logout, login as james (to see there is the gui or not)


(... Then, later, you can try if that (autologin) option appears for charlie in MX User Manager.)

[DukeComposed]

When I ask myself what I would do: Just try (at least to see) what happens if autologin enabled (though normally I don't prefer this)

I believe autologin is still going to prompt to unlock the user login keyring at the start of the X session.