First of all: I don't know exactly how to describe this problem, the first symptom I saw was an error on network connection after booting from a Live snapshot iso...
Not authorized to connect to my wifi network, also no action/response/startup for some MX Tools...
I'm using MX21.1_KDE_x64. The XFCE version doesn't give me these problems.
In the recent past I saw some similar problem description, but can't find this anymore.(69 y/o) The only word I remember from this is "chroot" plus some parameters...
Cheers!
authorization problem snapshot? some help needed
Re: authorization problem snapshot? some help needed
When creating the snapshot, did you check the box "Networks" ? (If yes, that's to "exclude" the connections (many times confused by users)).
On live session: What if you open "MX Tweak" (if it's working of course) - "Other" tab, and then change the "Pw. for administrative tasks" from user to root (or the vice versa)?
On live session: What if you open "MX Tweak" (if it's working of course) - "Other" tab, and then change the "Pw. for administrative tasks" from user to root (or the vice versa)?
Re: authorization problem snapshot? some help needed
@Huckleberry Finn
Thnx for the quick response!
For the first question, yes I did uncheck Networks, so included my Networks-settings.
I'll give your second question another shot, and let you know asap!
Cheers!
BTW I saw today an upgrade to 21.2; will also try this version from a fresh install, and will report my results...
Thnx for the quick response!
For the first question, yes I did uncheck Networks, so included my Networks-settings.
I'll give your second question another shot, and let you know asap!
Cheers!
BTW I saw today an upgrade to 21.2; will also try this version from a fresh install, and will report my results...
Re: authorization problem snapshot? some help needed [Solved]
referring to the second question: it didn't let me change user/root.
BUT:
a fresh install, then making a snapshot and reinstalling this, made the problem vanish like snow in the midday's sun...
So IMHO, this issue can be marked as SOLVED
BUT:
a fresh install, then making a snapshot and reinstalling this, made the problem vanish like snow in the midday's sun...
So IMHO, this issue can be marked as SOLVED