From: raingloom <raingloom@riseup.net>
To: 43985@debbugs.gnu.org
Cc: soheilkhanalipur@tutanota.com
Subject: bug#43985: Error logging in with non-Latin language
Date: Wed, 14 Oct 2020 18:13:21 +0200 [thread overview]
Message-ID: <20201014181321.55a5d212@riseup.net> (raw)
In-Reply-To: <MJ_OWoM--3-2@tutanota.com>
On Wed, 14 Oct 2020 06:37:32 +0200 (CEST)
soheilkhanalipur--- via Bug reports for GNU Guix <bug-guix@gnu.org>
wrote:
> After installing Guix system in non-Latin language, it is not
> possible to log in. When installing the system, the Guix system user
> login password was a "Persian" password; Once installed, the login
> page with my password will not open. (This is not a password error)
> To install on another system, I set an English password when
> installing, it worked properly and I logged in.
Does the installer use the same layout as the installed system?
That's usually what leads to these problems. I've had the same issue a
long time ago on Arch with Hungarian passwords.
Personally, I avoid passwords that can't be typed with ASCII, because I
might have to log in from someone else's machine and ASCII is the
lowest common denominator, for better or worse.
next prev parent reply other threads:[~2020-10-14 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 4:37 bug#43985: Error logging in with non-Latin language soheilkhanalipur--- via Bug reports for GNU Guix
2020-10-14 16:13 ` raingloom [this message]
2020-10-14 17:43 ` bug#43985: comment soheilkhanalipur--- via Bug reports for GNU Guix
2020-10-14 17:48 ` bug#43985: Error logging in with non-Latin language soheilkhanalipur--- via Bug reports for GNU Guix
2020-10-30 19:32 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-11-02 18:15 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-11-02 18:19 ` bug#43985: Done soheilkhanalipur--- via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201014181321.55a5d212@riseup.net \
--to=raingloom@riseup.net \
--cc=43985@debbugs.gnu.org \
--cc=soheilkhanalipur@tutanota.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).