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

    • I just looked on my computer and there are settings and log files for utilities I have never even turned on!
    • O&O ShutUp10 3.1.1104 by Razvan Serea O&O ShutUp10 offers a simple yet effective way to take control of your Windows privacy. It provides access to almost 50 privacy-related tweaks, most of them hidden or not easily accessible to the average computer users. Using a very simple interface, you decide how Windows 10/11 should respect your privacy by deciding which unwanted functions should be deactivated. Using ShutUp10 you can easily disable Windows Defender, turn off telemetry, disable peer-to-peer updates, turn off Wi-Fi Sense, disable automatic Windows updates, turn off and reset Cortana and more. ShutUp10 allows you to create a System Restore point before you apply any changes, so that you can revert your system at any time if you run into problems. O&O ShutUp10 is entirely free and does not have to be installed – it can be simply run directly and immediately on your PC. And it will not install or download retrospectively unwanted or unnecessary software, like so many other programs do these days! O&O ShutUp10 Free and Premium The latest version brings O&O ShutUp10 Premium, expanding the app’s long-standing privacy controls with automatic enforcement of user-defined settings. Instead of manually rechecking options after every Windows update, users can set their preferred privacy configuration once—or apply recommended settings in a single click—and the tool continuously monitors them in the background. If Windows 10 or 11 re-enables disabled features or introduces new data collection paths, Premium restores the chosen settings automatically without user intervention. The free version remains available and fully functional for manual adjustments, offering the same core privacy controls for Windows. However, the Premium tier is aimed at users who want long-term, hands-off protection, adding automatic reapplication after updates, ongoing monitoring, and optional notifications to ensure privacy settings remain consistent over time. O&O ShutUp10 3.1.1104 changelog: Added “Show Differences” button in the overview panel “Don’t show again” option for the restore point prompt Ctrl+F keyboard shortcut for search/filter functionality Detection and linking of system-wide and user-specific setting associations Automatic search while typing PREM: Option to preserve notification counters and timestamps across application restarts PREM: Reset blocked settings button in the Settings dialog PREM: Informational message when no settings are blocked PREM: Update check can also be triggered from the menu PREM: Notification deduplication and activity log summary feature Improved L005 “Disable Windows Location Service”: Version-specific split (up to Windows 11 23H2) and new variant for Windows 11 24H2+ L001 (Disable Location): Added Night Light warning to the description in all languages Search now detects setting IDs even when ID display is disabled and offers to enable it Detection and removal of Copilot/AI desktop apps in RecallTerminator Optimized High DPI support PREM: Reset button is now only enabled when blocked items exist – setting IDs are shown in the confirmation dialog PREM: Updated tray icons with higher-resolution versions PREM: Activity Log timestamps now use localized date and time formats PREM: Tray icon status now uses OK/Warning indicators and localized tooltips PREM: Recall folder detection switched to service-based detection PREM: Copilot uninstallation now provides UI feedback and improved verification Fixed Description text was not displayed correctly for the last item and disappeared when clicking the scrollbar Crash when clicking a search result heading or the […] button PREM: Installation path is now correctly preserved during upgrades PREM: Tray icon was not reliably removed when exiting the application PREM: Main window was not displayed correctly in single-instance mode PREM: Incorrect display of the & symbol in tray icon tooltips on Windows 10 PREM: Fixed notification flooding after sleep/standby PREM: Dashboard was not refreshed after applying recommended settings during onboarding PREM: Progress bar was not reset after deleting Recall folders PREM: Fixed service startup failures PREM: Fixed incorrect drift detection when Automatic Protection was disabled PREM: Notifications now correctly count all deviating settings when protection is enabled PREM: Registration Wizard was shown after sleep/standby despite a valid license Download: O&O ShutUp10 3.1.1104 | 76.4 MB (Freeware) Download: O&O ShutUp10 32-bit | ARM64 View: O&O ShutUp10 Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Fascinating...W h i t e P o w e r is now also asterisks out.  
    • In the past few days I have noticed two odd moderation activities. First, when I posted the term 'White Nationist Christian' it was asterisk's out. When I changed it to **** it was allowed! Second, in the Politics is a ###business thread I was allowed to post that the GOP is a party of p e d ophiles but I was censored  when I posted the GOP are a party of p e d ophile protectors. Wtf Neowin. Please explain.
  • Recent Achievements

    • One Month Later
      Vincian earned a badge
      One Month Later
    • First Post
      Jocimo earned a badge
      First Post
    • Week One Done
      suprememobiles48 earned a badge
      Week One Done
    • One Month Later
      Windows Guy earned a badge
      One Month Later
    • One Month Later
      Prasann earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      547
    2. 2
      +Edouard
      166
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Steven P.
      66
    5. 5
      ATLien_0
      64
  • Tell a friend

    Love Neowin? Tell a friend!