New Snapshot password problem recognized [Solved]

[fehlix]

I wanted to open thunar with root access. Something like sudo thunar or gparted (for what you need administrator rights) to manage the partitions for example.
In the last time it changed from typing "root" to "demo". I think, because the sudo operation is more secure than to log in as root.
But now it was not possible at all to log in as any user. The system didnt like that passwords.
So in clear: although I had made a snapshot for "everyone", the password needed to access any rights on the live system was not the announced "root" or "demo", but the one of my snapshot-producing system.

And the username on the installed snapshot-producing system, was not "demo", right?

[klamaux]

I think in all my 1000 linux installations I never used demo as username, but many different names
and my password was never the username. Perhaps next time...... :))

[dolphin_oracle]

could still use the log file. zip it up and attached to a forum message.

[klamaux]

could still use the log file. zip it up and attached to a forum message.

Just tried it once again after installing newest mx-snapshot ver. 22.10.05 : same problem

mx-snapshot.log.zip

Hope it helps

[klamaux]

Would like to know, if I am the only one who ran that thing with non functional passwords root and demo.
But I had a good experience, too:
Just tried to use F4 > Password at the start of the live-system.
This is running perfect and provides the (early) possibility for a secure password while browsing through the vastness of netspace.
Well made!

[Adrian]

Nothing out of ordinary jumps from that log to me. It would be interesting if in /etc/passwd on the new system you see "demo" or your old username.

[klamaux]

Nothing out of ordinary jumps from that log to me. It would be interesting if in /etc/passwd on the new system you see "demo" or your old username.

Hello Adrian, do you think the problem is only in my system?
When no one else got this problem, then it would be best, I do a complete reinstall from your actual iso (ahs).

When the problem ends with this, then you can mark the topic as solved.

So please tell me, if I am the only one with that problem. Thanks

[Adrian]

You ask me to tell you something I don't know, I don't know what's your problem that needs to be investigated, the user name is in /etc/passwd, the password is in /etc/shaddow... those are reset by "installed-to-live" script for user that has UID=1000 maybe you are using a different user id, not sure about specifics.

I also cannot tell you all the other users, I know this doesn't happen to me, but I don't think reinstalling is a solution, it might fix the issue, but if we don't know what is the parameter that is different in your case it will be just a workaround and it might happen again and we won't actually fix the problem.

Can you please provide a Quick System Info? That has some extra info that might gives us some clues, like default desktop environment, shell, etc.

[klamaux]

You ask me to tell you something I don't know, I don't know what's your problem that needs to be investigated, the user name is in /etc/passwd, the password is in /etc/shaddow... those are reset by "installed-to-live" script for user that has UID=1000 maybe you are using a different user id, not sure about specifics.

I also cannot tell you all the other users, I know this doesn't happen to me, but I don't think reinstalling is a solution, it might fix the issue, but if we don't know what is the parameter that is different in your case it will be just a workaround and it might happen again and we won't actually fix the problem.

Can you please provide a Quick System Info? That has some extra info that might gives us some clues, like default desktop environment, shell, etc.

Hi Adrian, have more computers with the same snapshot-password-tick.
Just inspected /etc/passwd : user is "demo" and in /etc/shadow are all entries after: the same exept root and demo, which have both more than 100 different units
Here my sysinfo

[dolphin_oracle]

did the root account password change to root? (the live system should always have a root account)