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 15: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?

Expand  

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 16: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.

Expand  

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 16: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 

Expand  

IDK, sadly..

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

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

IDK, sadly..

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

Expand  

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 18: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?

Expand  

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 18: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?

Expand  

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 23: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.

Expand  

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 19/08/2024 at 02: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..

Expand  

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 16: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

Expand  

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 13: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.

Expand  

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 14: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 

Expand  

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 15: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.

Expand  

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 17: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

Expand  

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 17: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.

Expand  

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 18: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

Expand  

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

  On 21/08/2024 at 13: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.

Expand  

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

    • Still won't get me in one, I prefer a human driver.
    • Sony's region restrictions on PC begin lifting, bringing back PlayStation ports for everyone by Pulasthi Ariyasinghe 2023 was when Sony began its region-locking initiative on the PC platform. The move affected over 100 countries, restricting the purchase of popular PlayStation ports and live service experiences for anyone in the regions outside of Sony's choosing. However, it seems the company is finally opening up access to these countries, starting today. While Sony has made no official announcements, which was also how the original restrictions came to be, users in these regions have begun seeing most of the publisher's catalog reappearing on their Steam store platforms. The change can be seen on affected games' SteamDB histories as well. For example, on Helldivers 2, a popular but blocked multiplayer game from before, it can be seen that the 'PurchaseRestrictedCountries' flag has been removed from a large number of countries just a few hours ago, on June 13. The controversy began in 2023 when Sony began requiring PlayStation Network accounts for their PC ports, even for games that did not have any online elements. Following an uproar, especially regarding Helldivers 2, the company reversed course and made it an optional account on PC. Unfortunately, Sony did not lift the regional restrictions it placed on the countries that do not officially support PlayStation Network accounts, which amounts to well over 100 regions. As for what may have changed the company's mind about this, Stellar Blade may have played a big role. The Sony-published action game by Shift Up just released on PC to an absolutely massive audience, with it already touting almost 200,000 concurrent players on the Steam platform. While its demo was originally region restricted, the developer had worked with Sony to remove these locks and launch the game globally. Just a few days later, almost the entire PlayStation catalog has gone through the same process. Interestingly, while massive PlayStation titles like Helldivers 2, God of War Ragnarok, Spider-Man 2, and The Last of Us Part II Remastered are back to being available across most regions, it seems Ghost of Tsushima is still under the original restrictions. It's unclear why the title has not joined the rest in shedding its locks.
    • Easy to switch off Ai on macOS, just a couple of clicks, something that is not possible on Windows, it is just hidden. Even Android it is possible at the moment to switch off AI, by not installing the app and keeping Google Assistant as it is. Not really possible to use anything else but IOS or Android for smartphones, since that is all that is available, unless I go for a non-smart phone. My problem, certainly with Windows, is that Ms thinks we all want to use AI and don't make it easy to disable. I only use my Windows machine for games these days and will be staying with Windows 10. I use my Mac for everything else, at least Apple gives the choice as i said above to turn AI off.
    • I think X3D is distinct from "X" alone, weren't most early X3D chips clock locked?
  • Recent Achievements

    • Explorer
      Case_f went up a rank
      Explorer
    • Conversation Starter
      Jamie Smith earned a badge
      Conversation Starter
    • First Post
      NeoToad777 earned a badge
      First Post
    • Week One Done
      JoeV earned a badge
      Week One Done
    • One Month Later
      VAT Services in UAE earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      537
    2. 2
      ATLien_0
      230
    3. 3
      +Edouard
      154
    4. 4
      +FloatingFatMan
      149
    5. 5
      Michael Scrip
      108
  • Tell a friend

    Love Neowin? Tell a friend!