Ubuntu install password always fails


Recommended Posts

I've never had luck with installing ubuntu desktop or server without the user created during setup not working...

I always have to boot into grub go in manually and set the password..... why? what am I doing wrong? I see this at home, at work, everywhere, even the latest version of desktop I tried last night... did a clean install from USB the created user and password set up, reboot.... wont log in... password is wrong...

do the same thing in a VM with server.... same thing... password wont work...

Why no mater what password I pick does the initially created user always fail? I've been down the reddit rabbit hole of explanations but everyone ends on "the user wasn't made right"... I've seen this since ubuntu version 20? and we're on 24 now? and the same issue every darn time....

Why does this happen?

On 18/08/2024 at 11:00, Nick H. said:

That's really weird...I can't say that I have ever seen that issue, and I've installed quite a few Linux systems, including Ubuntu.

What is your keyboard layout set to during setup and booting?

just the standard US keyboard layout... I know I'm not alone in this, since I've seen a lot of others complaining about it....and I am seeing it on multiple physical and any VM I try to do

Sadly, I have seen this, too.

I think what it is doing is overwriting the password, like you said.

I haven't used Ubuntu for years, so wasn't sure if this is still a bug. Apparently so.

On 18/08/2024 at 12:14, Mindovermaster said:

Sadly, I have seen this, too.

I think what it is doing is overwriting the password, like you said.

I haven't used Ubuntu for years, so wasn't sure if this is still a bug. Apparently so.

How is this bug stull there 4yrs after I first saw it happen? I don't get it how does anyone install this without having to go nuts 

On 18/08/2024 at 11:23, neufuse said:

How is this bug stull there 4yrs after I first saw it happen? I don't get it how does anyone install this without having to go nuts 

IDK, sadly..

Does this only happen when you install it, or after?

On 18/08/2024 at 12:33, Mindovermaster said:

IDK, sadly..

Does this only happen when you install it, or after?

only with the initial user you have to create during the install, after that if you go in through grub get in as the root user and do the passwd reassign it works fine

I've been using Ubuntu for my servers since about 2019~ish, I've never seen this issue. Also been running Ubuntu VM's a lot longer than that and have never seen this either :/ could it be an install media issue or possibly the wrong layout selected?

On 18/08/2024 at 13:21, Matthew S. said:

I've been using Ubuntu for my servers since about 2019~ish, I've never seen this issue. Also been running Ubuntu VM's a lot longer than that and have never seen this either :/ could it be an install media issue or possibly the wrong layout selected?

I think this problem began 3 years ago. So your version (running LTS, maybe?) didn't have that problem. Maybe? IDK..

Ubuntu has gotten weird over the years..

On 18/08/2024 at 14:21, Matthew S. said:

I've been using Ubuntu for my servers since about 2019~ish, I've never seen this issue. Also been running Ubuntu VM's a lot longer than that and have never seen this either :/ could it be an install media issue or possibly the wrong layout selected?

this has happened with every version I've used since 20.x up to the current 24.x desktop or server if its a media issue, its persistent across many versions, and I always use the US keyboard layout when it asks

What confuses me is that you mention it is every install that you make. I could understand one install every now and again, but every install?

No one likes to hear it, but I am thinking it's a PEBKAC issue. But I don't see how it could be installation media - how you load it onto a USB - if you enter the same issue through a VM.

Can you do a screen record going through a VM? That would help a lot.

On 18/08/2024 at 19:20, Nick H. said:

What confuses me is that you mention it is every install that you make. I could understand one install every now and again, but every install?

No one likes to hear it, but I am thinking it's a PEBKAC issue. But I don't see how it could be installation media - how you load it onto a USB - if you enter the same issue through a VM.

Can you do a screen record going through a VM? That would help a lot.

I can, but it wont be tonight, but like I said there are a lot of people complaining about this issue I can find examples of it on reddit now back all the way to 2015 at least

 

ex: here's someone having the same issue back in version 15, sheesh this is going back far: https://superuser.com/questions/943222/unable-to-login-to-ubuntu-with-my-user-password-that-was-created-during-installa

On 18/08/2024 at 22:42, Mindovermaster said:

Are these errors on one computer/server/VM? It might be an BIOS/UEFI setting. I'm not "sure" but hey, it could be anything..

I'm seeing this on at least 5 different physical systems and 2 different VM environments (proxmox and ESX)

Do you by chance use the Numpad when entering the numbers in your password?

The only reason I ask is Microsoft forced a change where numlock was off by default on system start up...

On 18/08/2024 at 12:34, neufuse said:

only with the initial user you have to create during the install, after that if you go in through grub get in as the root user and do the passwd reassign it works fine

I know no one wants to hear this but in my 30+ years in IT the issue has almost always been the password one is entering is NOT the same as the one originally created. It's as simple as that. Write down the password you want down (destroy later) before typing it in on creation. Don't use any characters that require the shift/Caps lock key beyond the minimum required.  Use actual words as a 4-5 word phase is more than enough security. Be aware of the CAPS lock and NUM Lock key when typing a password.

I have installed Linux and Ubuntu way to many times in my years and created passwords for countless other accounts. Every time I had a message the username/password is wrong it's because I entered it in wrong.

Edited by Good Bot, Bad Bot
On 21/08/2024 at 09:29, Good Bot, Bad Bot said:

I know no one wants to hear this but in my 30+ years in IT the issue has almost always been the password one is entering is NOT the same as the one originally created. It's as simple as that. Write down the password you want down (destroy later) before typing it in on creation. Don't use any characters that require the shift/Caps lock key beyond the minimum required.  Use actual words as a 4-5 word phase is more than enough security. Be aware of the CAPS lock and NUM Lock key when typing a password.

I have installed Linux and Ubuntu way to many times in my years and created passwords for countless other accounts. Every time I had a message the username/password is wrong it's because I entered it in wrong.

except, in this case it's not the issue.

Doesn't mater what the password is, can even just be password, it always fails every single time when its the initial user creation only, can be 0123456789 still fails when it's the initial one created in the install, but if I go in via grub at boot and set the password manually using passwd to the same exact one it works fine..

I can even repo this in vm workstation by using paste text to make absolute sure it's the same password copied from a text file and same issue still.

We just had it happen today again making a server install, password was copied from a password manager and pasted in via VMWare workstation connected back to our ESX host during Ubuntu setup initial user creation, and the password failed after the 1st reboot happened....

It's not just me having this, it's multiple techs here are seeing the same problem.. and it's only with Ubuntu, other distros no issue

 

Edit: ok so it's not even a password issue on the server, the user we specified on the initial setup isn't even being made on the server install... when we go in as root and look at the user list, they aren't even listed 

Edited by neufuse
On 21/08/2024 at 10:56, neufuse said:

except, in this case it's not the issue.

Doesn't mater what the password is, can even just be password, it always fails every single time when its the initial user creation only, can be 0123456789 still fails when it's the initial one created in the install, but if I go in via grub at boot and set the password manually using passwd to the same exact one it works fine..

I can even repo this in vm workstation by using paste text to make absolute sure it's the same password copied from a text file and same issue still.

We just had it happen today again making a server install, password was copied from a password manager and pasted in via VMWare workstation connected back to our ESX host during Ubuntu setup initial user creation, and the password failed after the 1st reboot happened....

It's not just me having this, it's multiple techs here are seeing the same problem.. and it's only with Ubuntu, other distros no issue

 

Edit: ok so it's not even a password issue on the server, the user we specified on the initial setup isn't even being made on the server install... when we go in as root and look at the user list, they aren't even listed 

I read a number of Linux sites, forums, and subreddits every day and never have seen this issue mentioned. It would be blasted every where if the problem as you describe it was happening on every Ubuntu install. Right? Can you point to a news article on it? A bug report? I am not asking for a post by a random person.

I am doing a new Ubuntu desktop install sometime this weekend and I will let you know.

On 21/08/2024 at 11:57, Good Bot, Bad Bot said:

I read a number of Linux sites, forums, and subreddits every day and never have seen this issue mentioned. It would be blasted every where if the problem as you describe it was happening on every Ubuntu install. Right? Can you point to a news article on it? A bug report? I am not asking for a post by a random person.

I am doing a new Ubuntu desktop install sometime this weekend and I will let you know.

There's a bunch of posts about it on Ubuntu's own forums and a bunch on reddit also... and from what it looks like the failure to make the initial user is happening a good bit...

and you want something odder, tried this on an AMD Epyc server now, worked fine 😶 all my issues so far are on Intel hardware and Intel VM hosts

On 21/08/2024 at 12:19, neufuse said:

and you want something odder, tried this on an AMD Epyc server now, worked fine 😶 all my issues so far are on Intel hardware and Intel VM hosts

That does actually makes sense. Intel always had trouble with Linux. Wasn't anything big, but, still..

Can I ask you why you need Ubuntu? IMO (and ONLY my opinion) Debian seems to run better on servers.. Even older ones.

On 21/08/2024 at 13:29, Mindovermaster said:

That does actually makes sense. Intel always had trouble with Linux. Wasn't anything big, but, still..

Can I ask you why you need Ubuntu? IMO (and ONLY my opinion) Debian seems to run better on servers.. Even older ones.

no specific reason, we just used it a lot before, but I'm just curious on what is causing this issue really

On 21/08/2024 at 13:49, neufuse said:

no specific reason, we just used it a lot before, but I'm just curious on what is causing this issue really

Well, seeing that Debian does not do this to you, it seems like an easy alternative.

On 21/08/2024 at 08:29, Good Bot, Bad Bot said:

I know no one wants to hear this but in my 30+ years in IT the issue has almost always been the password one is entering is NOT the same as the one originally created. It's as simple as that. Write down the password you want down (destroy later) before typing it in on creation. Don't use any characters that require the shift/Caps lock key beyond the minimum required.  Use actual words as a 4-5 word phase is more than enough security. Be aware of the CAPS lock and NUM Lock key when typing a password.

I have installed Linux and Ubuntu way to many times in my years and created passwords for countless other accounts. Every time I had a message the username/password is wrong it's because I entered it in wrong.

Yep, it annoys me when people use the caps lock key to capitalize a single letter.

Secure or not, if I have to type a password instead of having a password manager do it, I first type the password in Notepad, then copy and paste it below what I typed to ensure it has no space at the end, and then paste it in the password / confirm password box. This way, I could see the password and know it was typed precisely how I expected. However, that doesn't work so well for entering the password during an Ubuntu setup.

The problem people have is when it won't show you what you are typing or what you have typed, and you successfully fat-finger a password twice.

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • So its a museum of AI prompts? Boring
    • This one baffles me...so they are creating a museum based around the Ship of Theseus? A museum is supposed to preserve things. It doesn't really work if the conversation goes, "I gazed upon Starry Night the other day, the colours were beautiful!" "Yeah...I didn't expect Godzilla to show up, though." Create a building devoted to displaying AI work, fine. The rainforest idea sounds interesting and I would consider visiting if they pay me a few bucks. But don't call it a museum...
    • >defenders of AI-generated artworks often claim that AI is just a tool It is not. It is the inhuman artist replacement. The human writing the prompt is the employer/manager requesting the work product of the artist -- a supervisory/descriptive job that doesn't carry with it any rights to the copyright of that work product at all. And since AI is not human itself, it can't gain copyright for anything it is asked to regurgitate or hallucinate, so it can't transfer that copyright to the employer/manager/human who asked for the output. This was all legally reaffirmed last year. So, no, while there are AI tools, AI slopware generation is NOT a "tool" in the legal definition of that word.
    • As long as i get to play GTA 6 before it ends 😂😂
    • Google is opening the world's first AI museum in Los Angeles by Ivan Jenic Image via: Google Ever since AI image generators went mainstream, the debate over whether AI-generated art is real art hasn't let up. Those who don’t consider AI to be art say that if a machine does the creating and anyone can prompt it, there’s no skill involved, and therefore no art is produced. The counter-argument is equally persistent, as defenders of AI-generated artworks often claim that AI is just a tool, and that every major technological breakthrough, like the camera or the computer, was met with the same skepticism before eventually being accepted as a legitimate creative medium. Google’s position in this debate is clear. Which is no surprise, as the company is investing billions in AI infrastructure. And now, in efforts to encourage people to use its AI even more, Google is opening Dataland on June 20, which it's calling the world's first AI arts museum. Located inside The Grand LA, a Frank Gehry-designed building in Los Angeles, the museum spans 25,000 square feet. The museum is built around a collaboration with media artist Refik Anadol, who has worked with Google since 2016. The inaugural exhibition is called Machine Dreams: Rainforest, and is powered by an AI model trained on “an extensive dataset of the natural world.” It generates 1.2 billion pixels of visuals in real time and reacts to visitors dynamically. The space also generates soundscapes, real-time emotion sensing, and algorithmically produced scents. Image via: Refik Anadol Studio / Google Google says that the museum is powered by its Gemini models, which run on Google Cloud. So, everything is generated inside one of Google’s AI data centers and is streamed to the museum. Alongside the museum opening, Google Arts & Culture is funding an AI Artist Residency, giving four artists $25,000 grants each, along with mentorship from Refik Anadol Studio and access to Google's machine learning tools. Their work will be shown at Dataland and on the Google Arts & Culture website later this year. Google’s AI museum will undoubtedly initiate a fired-up debate on social media, and we can’t wait to see the first reactions. Via: Smithsonian Magazine
  • Recent Achievements

    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      570
    2. 2
      +Edouard
      178
    3. 3
      PsYcHoKiLLa
      74
    4. 4
      Michael Scrip
      68
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!