From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Pon Arun Kumar R <ponarunkumar@gmail.com>
Cc: 38447@debbugs.gnu.org
Subject: bug#38447: Guix Stand-alone OS installation Error - T410 - x86 - intel - lenova
Date: Mon, 02 Dec 2019 15:14:07 +0100 [thread overview]
Message-ID: <87zhgake6o.fsf@gmail.com> (raw)
In-Reply-To: <CAHWdhg8O6J9mF1LKwFgNgBOt_RtmWd3Mt5saXFkb6FfhCrR0iA@mail.gmail.com>
Ok thanks. Did you use 1.0.1 image from http://guix.gnu.org/download/?
Mathieu
Pon Arun Kumar R writes:
> Hi Mathieu,
>
> I tried selecting two different locale/keymap config in two different
> attempts, 1. on the regular US english intl and 2. regular US eng,intl with
> dead keys,
>
> I tried several attempts, and I doubt whether it is something to do with
> the BIOS settings update as a pre-requite for the installation.
>
> Thanks,
> Pon ArunKumar R
>
> On Mon, Dec 2, 2019 at 8:54 AM Mathieu Othacehe <m.othacehe@gmail.com>
> wrote:
>
>>
>> Hello!
>>
>> > Could you please help in resolving this issue?
>> >
>> > “Unable to locate key map update file”
>>
>> Thanks for your report. Which locale/keymap did you choose before this
>> error occured?
>>
>> Mathieu
>>
next parent reply other threads:[~2019-12-02 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41265364-ABBC-438C-9BBA-9FBC3DB04B9D@gmail.com>
[not found] ` <874kyiltop.fsf@gmail.com>
[not found] ` <CAHWdhg8O6J9mF1LKwFgNgBOt_RtmWd3Mt5saXFkb6FfhCrR0iA@mail.gmail.com>
2019-12-02 14:14 ` Mathieu Othacehe [this message]
2019-12-02 14:18 ` bug#38447: Guix Stand-alone OS installation Error - T410 - x86 - intel - lenova Pon Arun Kumar R
2019-12-11 16:08 ` Pon Arun Kumar R
2019-12-13 16:47 ` Mathieu Othacehe
[not found] ` <023E12E8-B8A4-4421-8E58-2F3DEA15F84F@gmail.com>
2019-12-14 14:13 ` Mathieu Othacehe
2019-12-19 16:20 ` Ludovic Courtès
2019-12-11 17:09 ` bug#38447: Instructions to reproduce the issue Brice Waegeneire
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=87zhgake6o.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=38447@debbugs.gnu.org \
--cc=ponarunkumar@gmail.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 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.