ice-9/eval.scm:159:9: Unable to locate keymap update file

  • Done
  • quality assurance status badge
Details
3 participants
  • Ludovic Courtès
  • Mathieu Othacehe
  • Mortimer Cladwell
Owner
unassigned
Submitted by
Mortimer Cladwell
Severity
important
Merged with
M
M
Mortimer Cladwell wrote on 12 May 2019 09:51
(address . bug-guix@gnu.org)
CAOcxjM52kbdNEyZ5Y4BPQ0qJaqwzN5twA07iMkSePugrNo_m7Q@mail.gmail.com
Hello,
I am using:
guix-system-install-1.0.0.x86_64-linux.iso
Dell Latitude E5500
ATA Hitache HTS72328 (scsi) /dev/sda 80GB disk
wired ethernet 00219be81197 cable
Graphical install
Bottom line error message: ice-9/eval.scm:159:9: Unable to locate keymap
update file
Some hopefully useful screen shots attached.
Thanks
Mortimer
Attachment: file
Attachment: guix-errors.zip
L
L
Ludovic Courtès wrote on 13 May 2019 09:38
(name . Mortimer Cladwell)(address . mbcladwell@gmail.com)(address . 35700@debbugs.gnu.org)
87y33avm6o.fsf@gnu.org
Hi Mortimer,

Thanks for reporting these issues.

The “Unable to locale keymap update file” presumably occurs when trying
to restart the installer after a failed install, which is unfortunately

Your screenshots also show that the ‘xlockmore’ package couldn’t be
built, specifically derivation
/gnu/store/zvlbagr7vvawd0qk8444slrn8cnnamh6-xlockmore-5.56.drv.
Unfortunately, I do not know why that happens; the exact same package
builds fine for me.

The last screenshot (where we can see “/bin/sh: Command not found”, and
which ends with a “root@gnu” prompt) looks interesting, but it lacks
context. What command did you type to obtain this output?

Thanks,
Ludo’.
L
L
Ludovic Courtès wrote on 15 May 2019 13:52
control message for bug #35700
(address . control@debbugs.gnu.org)
87bm04vsrr.fsf@gnu.org
severity 35700 important
L
L
Ludovic Courtès wrote on 15 May 2019 13:53
control message for bug #35690
(address . control@debbugs.gnu.org)
87a7fovsqw.fsf@gnu.org
merge 35690 35700
M
M
Mathieu Othacehe wrote on 18 Mar 2020 19:06
Fixed
(address . 35700-done@debbugs.gnu.org)
87mu8dczbm.fsf@gmail.com
This has been fixed by 64704be417ab6f2788e8e3bc36fede1db35470e7.

Thanks,

Mathieu
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 35700@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 35700
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch