From: o.rojon@posteo.net
To: 37897@debbugs.gnu.org
Subject: bug#37897: Bug: Resetting locale settings
Date: Thu, 24 Oct 2019 00:49:36 +0200 [thread overview]
Message-ID: <86c252b08059f9b678e0389bacc3a065@posteo.net> (raw)
Hello guix,
I believe that a locale-related bug has slipped in somewhere in the last
two-three weeks. During installation and in my configuration file, I
have specified de_DE specified as locale, which should translate to a
german keyboard layout. But since said two-three weeks, I startup with
what I believe is the US layout (qwerty) - and before this occurred, I
was once even unable to login because my keyboard layout has been
changed to something so obscure it didnt even seem to know basic
characters like the exclamation mark, while there was a number of
characters that could not be displayed (probably non-utf characters I
suppose).
In the latter case, I was able to login via 'loadkeys
/run/current-system/profile/share/keymaps/i386/qwertz/de-latin1' in TTY
(where I went with C-M-F2 or F3, nvm); but now, I am unable to set the
keymap via loadkeys. When I dont use sudo, I receive the message 'data
descriptor referring to console couldnt be found' (translated from
german "Dateideskriptor, der auf die Konsole verweist, konnte nicht
gefunden werden."); if I do use sudo, I dont get an error, but the
keyboard layout doesnt change.
I really dont know what I could've contributed to produce such a
situation. The only thing I noticed is that it KIND OF coincides with me
installing glibc to make guile stop nagging that "locale couldnt be
found" (or something like that).
Obviously, help would be appreciated :)
Greetings!
next reply other threads:[~2019-10-23 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 22:49 o.rojon [this message]
2019-10-23 23:27 ` bug#37897: Bug: Resetting locale settings Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-25 20:44 ` Ludovic Courtès
2019-10-26 21:26 ` o.rojon
2019-11-13 13:48 ` Ludovic Courtès
2019-11-14 12:23 ` o.rojon
2019-11-14 21:51 ` Ludovic Courtès
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=86c252b08059f9b678e0389bacc3a065@posteo.net \
--to=o.rojon@posteo.net \
--cc=37897@debbugs.gnu.org \
/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).