I remember you, how did you go with your raspi project? Looking forward to your updates!
/etc/passwd: you may be able to get to this from the GUI file manager.
If not, open a terminal and type: cat /etc/passwd. Copy the relevant lines.
To test the login, from a terminal, type su otheruser, replace otheruser with the username from /etc/passwd. It should ask for a password, put that in and it should log you in. Type whoami and make sure its the same username as you expected. Paste any errors here.
I want a modern Flatout 2, such a fun game.
"Group policy me harder, babe"
I think that was meant to be a reply to me, so I'll respond.
Technically, /etc/passwd can have encrypted passwords in it, but as far as I'm aware, no distro has done that in decades, so realistically its not that risky. It does expose the user names though.
Can you share the lines from /etc/passwd for your user and the user your adding? Despite its name, there are no passwords here, that is in /etc/shadow
Edit: can you su to login as the user?
Don't windows-shame me!
I prefer to think of it as an open relationship. I have my home distro, my work distro, and if either of them aren't in the mood, there is an wide variety of other distros to get the job done.
And if I'm feeling really kinky, there's always Windows.
Its not a browser thing, its HTTP. The return codes are specific to the request, not the server.
GET example.com could validly return 403, while GET example.com/tracking123.gif returns 200 or anything else.
Yes, the server gets the request for /uniqueForTracking/b19...184.gif, which could be logged.
403 means you still hit their server, and it could well have been logged.
Its not for you, its for spammers...