From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 35806@debbugs.gnu.org
Subject: bug#35806: Login passwords incorrect on some newly installed 1.0.1 systems
Date: Mon, 20 May 2019 22:36:32 +0200 [thread overview]
Message-ID: <87imu4q2wf.fsf@gnu.org> (raw)
In-Reply-To: <20190520200251.34xfc6ik53hr6z5k@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Mon, 20 May 2019 22:02:51 +0200")
Hi,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> However, the second install had no normal user account, as you can see
> in my /etc/shadow (which is attached again). It should not have been
> possible to install without user account. Now that I think about it,
> I believe when I got shown the user account creation page in the
> installer, I accidentally immediately pressed some key (maybe Enter)
> and it threw me back to the locale selection. I configured everything
> again, but I believe this was the reason no user account was created.
>
> I could now make the user account creation page crash again by
> entering a wrong password confirmation, but after going through the
> installer again, the resulting config contains a user and I can login.
> I do not know how I managed to break this.
Could you file a bug specifically for this one if you managed to
reproduce it?
>> Note that you can check by doing an install in a VM using the attached
>> script.
>>
>
> Thank you. For now I’ll try on real hardware though.
Well that’s even better. :-)
Should we consider this bug closed?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-05-20 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 9:38 bug#35806: Login passwords incorrect on some newly installed 1.0.1 systems pelzflorian (Florian Pelz)
2019-05-20 15:01 ` Ludovic Courtès
2019-05-20 20:02 ` pelzflorian (Florian Pelz)
2019-05-20 20:36 ` Ludovic Courtès [this message]
2019-05-20 20:41 ` pelzflorian (Florian Pelz)
2019-05-27 10:03 ` Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imu4q2wf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35806@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.