[maverick] wrong keyboard layout in live or ubiquity session
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| casper (Ubuntu) |
Triaged
|
Critical
|
Unassigned | ||
Bug Description
Binary package hint: ubiquity
1)
Description: Ubuntu maverick (development branch)
Release: 10.10
2)
ubiquity:
Installed: 2.3.13
Candidate: 2.4.4
Version table:
2.4.4 0
500 http://
*** 2.3.13 0
100 /var/lib/
3) While doing advanced partition editing (assigning drives manually to mount directories) I expect to be able to use my own keyboard layout (in my case German)
4) Instead I had to use an English keyboard layout, making adjustments to paths quite difficult (had to copy the symbol '/' with Ctr+C and Ctrl+V, otherwise it would not have been possible to adjust paths manually). Only later in the installation process can I adjust the keyboard layout.
This is probably not a ubiquity bug but a problem of a problematic ordering of the installation process (chosing keyboard layout after partitioning).
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubiquity 2.3.13
ProcVersionSign
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Wed Sep 29 13:21:50 2010
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
Related branches
| Prunus dulcis (prunus-dulcis) wrote | #1 |
| Didier Roche-Tolomelli (didrocks) wrote | #2 |
| summary: |
- [maverick] wrong keyboard layout for partition editor + [maverick] wrong keyboard layout in live or ubiquity session |
| affects: | ubiquity (Ubuntu) → casper (Ubuntu) |
| Changed in casper (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| milestone: | none → ubuntu-10.10 |
Thanks for reporting this bug and help to make Ubuntu better.
The issue appears when 19keyboard is executed in casper-bottom. This one fails with:
Begin: Setting up console keyboard... ... Illegal instruction
Illegal instruction
Illegal instruction
done.
The issue is, when testing in the initramfs:
chroot /root sed -i "s/foo/bar" foo
Illegal instruction
chroot /root /bin/sed -i "s/foo/bar" foo
works
However, I'm puzlled as:
chroot /root which sed
return /bin/sed (isn't which internal to dash in this initramf and then, don't find it?)
Preparing the fix now.