Whatever.
Because:
the machine name doesn’t matter -
not at all,
not a tiny bit,
not in the slightest
Am I right that, when I gather from your last post, that everything is all right now?
Is there a current problem?
If the answer is “yes”:
What is it?
(let’s try to not do forensics
without anything “tangible” right now)
There is, but not related to this post.
As expected, it shouldnt, I said cause this type of problems used to be commons 20 years ago, where the devs didnt expected the user to set a particular name and everything stopped working because of that, or similar stuff.
If needing to reinstall the OS every week is right, then yes it is.
That is not an answer to the question.
I detect a passive aggressive one.
Is there currently a problem or is there not?
It’s a simple to answer question.
Don’t quote only what is convenient to you. I answered your question and quoted your question.
Just solved this issue, so exactly now no.
I am not the one who have disrepected anybody.
Your questions though have been answered multiple times in the forum. Hadn’t complained cause it is a long post, and you may not want to read it (understandable) even though I set references all the time for easier read.
Quite the opposite of what is commented here to this post Linux is NOT Windows.
A lot of questioning about checking over and over if the password is correct. (Understandable, the problem described is so amazingly rare and hard to believe that happened, I even thought I forgot my password, and the first thing I did was to change it with chroot, but the problem appeared back, also I had the password written on paper in such cases, but my fault was obviously my first thought).
I hadn’t shown any disrespect towards anybody, I am new to linux not to programming, if you expect me to be an idiot that knows nothing and ask for help on the first thing that comes to its mind I am not, I asked here in the forum cause this problem is overwhelmingly strange and hadn’t found anything similar (understandable).
If you just want me to leave cause you don’t want to deal with “newby” say it.
¿Is this straightforward enough to you? I doubt it.
Most forum members are willing to take time out of their days to help users experiencing issues, regardless of how “easy” the question may be (or may not).
But from the likes of your tone and passive aggression, fewer and fewer people are going to want to contribute. No one is questioning you or your skills. We are as lost as you make us be 
.
You have not made your situation clear to us. How can we help you if you do not provide us the necessary information to work with? I read the entire thread and I still don’t know what you want exactly. I understand communication over text can be tricky at times, but if you ask a question, expect to answer follow-up questions from those trying to help out.
Anyhow, from the looks of things, it appears you have reinstalled Manjaro and are dual booting with Windows. You are since able to login successfully, but:
What does that mean?
If you have removed the install medium
What if you - by accident of course - have written the install medium to your systems harddrive instead of USB?
No matter how may times you may experience this - the username and/or password does not change by itself.
Just as 0 + 0 = 0 just the same is with password and/or username - it only changes by interaction.
The right questions are
If the answer is no-one - then there is only you - no updates ever changes your system.
This was a tough read, but I’ll admit, turned into a skim.
As said, passwords don’t change themselves. There must be something you are doing which in your mind is 100% correct, but in this ecosystem may not be? Just my useless guess at the most likely cause.
As for tracking it down. I don’t know of a way to change the password without it being logged. So find it.
man journalctl will be your friend.
To start, you can do: journalctl | grep -E 'passwd|pam_'
Lots of options like the -b/–boot option, so you could put journalctl -b0 instead for the logs from when you turned it on. (-b -1 for the boot before that, -r/–reverse, etc.)
In Gnome, I see gdm-password entries as well, which the above would miss. So whatever DE you run, and there are probably other ways to change it (but shown in the logs).
That’s all I got.
Fast Startup is not a BIOS option to disable. You are confusing this with Fast Boot, which is something totally different. Incidentally, it’s often recommended to disable Fast Boot also, when booting Linux (irrespective of it being part of a multiboot scenario).
These two terms are frequently confused by many, including forum Moderators, who should probably know better. Disabling Fast Startup in Windows is absolutely required when multibooting.
Again, you seem to be confusing the two.
Fast Startup has existed since Windows 8.0/8.1. It’s a Windows-only version-specific feature which indeed had not existed prior to those Windows versions. It’s in essence a hibernation variant included by Microsoft.
Fast Boot is a BIOS option which has existed for up to 30 years (but not in all brands/combinations). Fast Boot (if present, and enabled) allows certain self-tests to be skipped during pre-boot (before handoff to a bootloader).
It was a possibility; and if you had read your earlier comments from this perspective, you would no doubt have considered that aswell.
Now, it does seem to be more obviously a language issue. Despite what you may or may not think about language translators, Google Translate (or similar) might have been beneficial.
Even moreso, considering some members are already doing the best they can to translate from English to their own respective language, without adding Spanish into the mix. Much can be lost in the process; language degeneration; I’m sure you appreciate the concept.
After skimming the last few posts I see further misunderstandings, with each party seemingly convinced of having not contributed to it.
I have offered some input, as have others, but this thread seems to be going nowhere fast. It just keeps returning to “the password changed itself” which we are all (yourself included) painfully aware, cannot happen.
Indeed, as this does not (can not) happen, there are also no other cases to compare it with; certainly not in my experience. The issue is therefore something specific to you.
Further. Now that you have apparently reinstalled all instances of the OS in question, the point of this thread is moot until such time that any issue might manifest again.
Until that time, you can no longer provide any actionable information, let alone anything that might help diagnose more than conjecture.
I suggest this thread (already at 27 posts) be closed, and invite the OP to open a new support request if/when the issue again returns, and relevant logs are possible.
Cheers.
You are assuming that all moderators would also be Windows users – an assumption sprung forth from the erroneous but unfortunately very stubborn misconception that GNU/Linux is — or was developed as — an alternative to or substitute for Microsoft Windows, a platform from which it couldn’t possibly be farther removed.
GNU/Linux was developed as an alternative to the proprietary UNIX systems of the day, and this was specifically the case for the GNU components of the system.
The Linux kernel was developed as an alternative for the Minix kernel, because Minix was only a 16-bit system at the time, and its license did not allow modification of the source code, while Linus Torvalds — who had been using Minix — wanted to have a 32-bit UNIX system on his computer.
I agree. Time to get off the merry-go-round.