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

    • We now know when and how the Universe may truly end by Sayan Sen Image by Marek Pavlík via Pexels| Not representative A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. The research, published in the Journal of Cosmology and Astroparticle Physics, was conducted by Tye, Horace White Professor of Physics Emeritus at Cornell University. Using recent observations from major dark-energy surveys, Tye and his collaborators developed a cosmological model that predicts the universe could have a total lifespan of about 33 billion years. Since the universe is currently estimated to be 13.8 billion years old, the model places it near the midpoint of its existence. According to Cornell University's summary of the research, the study centers on the cosmological constant, a term introduced by Albert Einstein in his theory of general relativity. In modern cosmology, the cosmological constant is commonly used to describe the simplest form of dark energy, the unknown phenomenon believed to be driving the accelerating expansion of the universe. "For the last 20 years, people believed that the cosmological constant is positive, and the universe will expand forever," Tye said in a Cornell University news release. "The new data seem to indicate that the cosmological constant is negative, and that the universe will end in a big crunch." The study draws on data from the Dark Energy Survey (DES) and the Dark Energy Spectroscopic Instrument (DESI), two major projects designed to investigate the nature of dark energy. According to Tye, recent observations suggest that dark energy may not behave exactly like a simple cosmological constant. To account for those observations, Tye and his collaborators proposed a model involving an extremely light hypothetical particle that evolves over time. In their calculations, this produces a negative cosmological constant and leads to a future collapse of the universe. The model predicts that cosmic expansion would continue for approximately another 11 billion years before reaching a maximum size, after which the universe would begin contracting and eventually collapse. Scientists have long debated how the universe might end. As explained in an article published in The Conversation by Stephen DiKerby of Michigan State University, several possibilities have been proposed. If dark energy remains constant and positive, the universe could continue expanding indefinitely, gradually becoming colder, darker and more diffuse in a scenario often called the "heat death" of the universe. Other theoretical possibilities include a Big Rip, in which cosmic expansion accelerates so dramatically that galaxies, stars and even atoms are torn apart, or a Big Crunch, in which expansion reverses and the universe collapses back into an extremely dense state. DiKerby notes that the Big Crunch idea itself is not new. What distinguishes Tye's work is that it attempts to use current observational data to estimate when such a collapse might occur and how it could unfold. Much of the universe's long-term evolution remains uncertain. According to current astrophysical understanding, stars will continue to form and die for billions of years. The Sun, for example, is about halfway through its expected lifespan. Galaxies are also expected to continue merging; the Milky Way and Andromeda galaxies are projected to collide several billion years from now. At the same time, the nature of dark energy remains one of the biggest unanswered questions in cosmology. While observations indicate that the universe's expansion is accelerating, scientists still do not know what is causing that acceleration. Future observations may therefore alter current predictions about the cosmos's ultimate fate. Tye emphasized that additional evidence will be needed before firm conclusions can be drawn. DESI continues to collect data, while upcoming observations from missions and observatories including Euclid, SPHEREx and the Vera C. Rubin Observatory are expected to provide more precise measurements of dark energy. "People have said before that if the cosmological constant is negative, then the universe will collapse eventually. That's not new," Tye said. "However, here the model tells you when the universe collapses and how it collapses." For now, the study presents one possible future for the cosmos rather than a settled prediction. Whether the universe ultimately ends in a Big Crunch, expands forever, or follows another path entirely remains an open question that future observations will help answer. Source: Cornell University, The Conversation This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • If you look around on Amazon, some of these are available for $9
    • I’m still using an Xbox One S, so time for an upgrade to play this but as much as I hate Sony, I think I’ll get the ps5 pro
    • I bought this game. Played it for an hour, and then got a refund from Steam. Not a fun game at all.
    • Nothing Ear buds with active noise cancellation are at their lowest price ever with 51% off by Fiza Ali Amazon is currently offering the Nothing Ear wireless earbuds at their lowest price ever with 51% off limited prime deal. The earbuds feature an 11mm dynamic drivers with a ceramic diaphragm, and support high-resolution audio codecs including AAC, SBC, LDAC, and LHDC 5.0. They support active noise cancellation of up to 45dB across a frequency range of up to 5000Hz, and include a smart ANC algorithm, adaptive noise cancellation, and a transparency mode that allows surrounding sounds to be heard when needed. Connectivity is provided via Bluetooth 5.3, with support for multiple profiles including HFP, A2DP, AVRCP, and others. The earbuds also support dual connection, allowing them to be paired with two devices at the same time. Additional features include IP54 water and dust resistance for the earbuds and IP55 for the charging case, in-ear detection, pinch controls, low-latency mode, Google Fast Pair, Microsoft Swift Pair, and a three-microphone system per earbud for clearer voice calls. The Nothing X app, available on Android and iOS, provides access to custom EQ settings, bass enhancement, personal sound profiles, ear tip fit testing, firmware updates, customisable controls, dual-device management, and a find-my-earbuds feature. In terms of battery performance, each earbud has a 46mAh battery and the charging case has a 500mAh capacity. With active noise cancellation (ANC) turned off, the earbuds should offer up to 8.5 hours of playback on a single charge and up to 40.5 hours in total with the charging case. With ANC enabled, playback should last up to 5.2 hours on the earbuds and up to 24 hours with the case. For calls, talk time should reach up to 5 hours on the earbuds and 23 hours with the case when ANC is off, while ANC on should provide up to 4 hours on the earbuds and 18 hours with the case. Finally, fast charging should deliver up to 10 hours of playback from 10 minutes of charging when ANC is disabled. Nothing Ear Wireless Earbuds Bluetooth: $73.15 (Amazon US) - 51% off Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
  • 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
      572
    2. 2
      +Edouard
      173
    3. 3
      PsYcHoKiLLa
      73
    4. 4
      Michael Scrip
      68
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!