|
This can no longer be a coincidence.
I've lost count of the number of times where I've installed a Linux distribution on this old laptop of mine (which I primarily keep to tinker with different Linux distributions), I create my login username/password, everything's fine, then upon the first reboot...my password is rejected as if I've made a typo.
Yet if I type it into the username field, just to be able to view the individual characters (and ensure it's not a caps-lock type of thing), I can confirm I'm entering it correctly. This has happened with multiple versions of multiple distributions. Yet I've never had this happen with Windows. I always use the same password so I can type it reliably with muscle memory.
The laptop I'm installing Linux on isn't being used for anything particularly important and doesn't contain any important data, so my workaround, when this happens, is to reinstall (!) and then to simply set the password as 'password'. Pretty lame, but I swear, if I use a combination of uppercase/lowercase, digits, symbols, etc then any login attempt after the initial OS install fails to recognize it. It makes absolutely no sense, and I feel crazy just writing this down to ask if anyone's ever seen this. It has happened so many times to me it cannot be mere coincidence.
Am I losing my mind?
|
|
|
|
|
Could it be the keyboard layout? If it defaults to US layout for installation, and then changes to another layout when you reboot, the symbols may have moved. 
(Or have you already tried the "type it in the username box" trick both at creation and login?)
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I thought about that, but I don't change the keyboard layout. And yes, I did try temporarily entering the password in a field so it's visible both during the setup, and after. Like I said - zero sense.
|
|
|
|
|
Are you trying to logon as root ?
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
modified 17-Dec-22 3:56am.
|
|
|
|
|
I'm trying to login using the credentials I've supplied during the OS setup.
|
|
|
|
|
Check your keyboard-settings and the keyboard itself; I've had the same problem, a few times. One that always gets me is a Norwegian laptop I have, with the keyboard set to EN-US. Most of the characters are then where I expect them to be. Very confusing at the time I worked in Germany, where z and y are swapped.
Another time it happened simply because the keyboard needed cleaning. Sometimes an "e" came when typed, sometimes no "e", sometimes two or three. That's the downside of smoking behind your computer.
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Are you using any special characters like < > | etc?
That might mess up a shell command/sed/regexp etc?
The setup might be collecting info into a template that barfs when it tries to read it back.
|
|
|
|
|
Not those characters specifically, but I do have some non-alphanumeric characters...but nothing that would even be rejected as part of a filename.
englebart wrote: The setup might be collecting info into a template that barfs when it tries to read it back.
I suppose if the installer is using one validation routine, but the login code uses something that's not 100% identical...that could mess things up? But you'd think this sort of thing would've been found/fixed - my password isn't that sophisticated...but who knows.
|
|
|
|
|
dandy72 wrote: Am I losing my mind?
Yes
Jeremy Falcon
|
|
|
|
|
Well...that was a rhetorical question. And I kinda already knew the answer to it. 
|
|
|
|
|
Ok, for a real reply. Just assuming you're installing a distro that gets a GUI going by default.
If that's the case, then reboot into the console or single user mode if you know the root password. The switch user (su) command can be use for more than just root access. So, try something like this:
Quote: su - user2
If you can't login that way, there's a problem with your password.
And if that's the case, what you can do to make sure it's not the install process is create a second user after a fresh install and before you reboot. See if you can login with that user instead afterwards. If you can, then maybe the install process messed something up.
Jeremy Falcon
|
|
|
|
|
The problem is that the distro doesn't prompt you to create a root account and doesn't document what the default root password might be. Going through the entire installation process, I'm only ever prompted to create one set of credentials. Since those are no good, after a reboot...I'm basically completely locked out.
|
|
|
|
|
If that's the case, I'm willing to bet (hoping to bet) the install puts the default account as a sudoer. So, you should be able to run sudo su without needing the root password, to gain root access.
Jeremy Falcon
|
|
|
|
|
...right? But if I can't even reach a command prompt (because I have to login), how would I run sudo su at all?
|
|
|
|
|
You don't have access to the machine before the reboot? What distro is this?
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: You don't have access to the machine before the reboot? What distro is this?
Not sure if I've explained this right.
Clean hard drive, I boot from an ISO, and run the distro's installer. At some point, it'll ask you for credentials, and it creates that account. You're not prompted to supply a password for the root account. That means the distro creates the account you've just supplied credentials for as part of the sudoers list.
Finish the install, reboot, you have to supply credentials to login. That's when the password I had initially supplied is simply not recognized. Can't reach a command prompt to run sudo or anything else.
The laptop I was tinkering with was running some instance of Fedora at one point. Then it was running Zorin. Then (and this is where I did my tinkering last week) I installed Lubuntu. They all had the same problem.
|
|
|
|
|
I don't use any Ubuntu variants, but what happens if you install Debian directly without the GUI installer, using the ncurses installer? Never once ran into that issue with Debian, so if you do then there's gotta be another reason than the install process.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: if you install Debian directly without the GUI installer, using the ncurses installer?
I'm just a guy who happens to tinker with Linux every once in a while, by booting from the ISO and following the prompts on the pretty wizard screens. If I have to get my hands more dirty than this, this early in the process, it's not likely to be a distribution I'll be spending time with.
I mean, I've installed plenty of Debian versions, and derivates of it, but "without the GUI installer, using the ncurses installer", is mostly gobbledygook to me. I'm not that dedicates to it, and I'm happy for now with my solution...
I do appreciate the suggestions however.
|
|
|
|
|
We've all heard of application "bloat". What we're seeing now is starvation.
I would sometimes watch my users in action and see them using my app in ways I had not anticipated; like "multiple concurrent sessions".
In the pursuit of "the one and only app", one person thinks they know what everyone wants and needs, and in the process is eliminating "features" that certain groups found useful, but that would never dawn on said former person; in fact, said person considers said feature a "personal" problem.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
It depends I guess, would rather have a "starvation" app that just works than one with all kinds of bells and whistles that are buggy.
Doing a lot of starvation thingies for our application that has lots of features that are hard or impossible to implement in .NET 6.
|
|
|
|
|
But... surely you're not implying that the latest version of .Net is harder to code, or less functional, than earlier versions??  
|
|
|
|
|
Yep, I find it harder because I'm responsible for packaging everything so users can install it easily and it is often a complete mystery what runtime flavors need to be installed for instance. I often think back how easy things were with .NET 4.8. I have to admit that our main application is a complex mish-mash of more than 150 projects with C++, C#, lots of NuGet and 3rd-Party libraries.
A lot of time and effort already has been invested in the upgrade from .NET 4.8 to .NET 6 and some colleagues naively thought it was nearly completed proclaiming: "it runs on my machine". But sadly we still have a long and painful way to go before things can be installed properly and testing has completed.
|
|
|
|
|
...where you can specify the date and time to send a message.
Snazzy! I can send messages when I'm not working. People will think I'm working!
[edit]Doesn't work with the web version of Teams. I just get the standard browser right-click popup menu. Bummer.[/edit]
|
|
|
|
|
All this technology, and we end up using it to randomly interject with a "yes, dear"
|
|
|
|
|
I'll send you a message about that.... later.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
