On 26/12/2009 22:47, Eric Valette wrote:
I finally found the bug: I traced setupcons -k in error mode and it
expects to find ckbcomp but unfortunately /usr is not mounted and
ckbcomp is /usr/bin/ckbcomp
I traced the setupcons -k with set -x and it exist with doing anyting
because it does not
On Sun, Dec 27, 2009 at 10:01:00AM +0100, Eric Valette wrote:
On 26/12/2009 22:47, Eric Valette wrote:
I finally found the bug: I traced setupcons -k in error mode and it
expects to find ckbcomp but unfortunately /usr is not mounted and
ckbcomp is /usr/bin/ckbcomp
I traced the setupcons
On 27/12/2009 13:20, Anton Zinoviev wrote:
Indeed copying ckbcomp to /bin instead of /usr/bin fixes the problem.
Yes, I can confirm this. Setupcon tests the existence of ckbcomp even
when it doesn't require ckbcomp. Thanks for the debugging.
When this bug is fixed (maybe in the next
On Sun, Dec 27, 2009 at 01:58:00PM +0100, Eric Valette wrote:
Will try to remember it when I receive the notification for the bug
being closed. Now, I that I cured the side effect, I have to cure
the real problem, that is, why checkfs script always returns an
error even if the FS are good
On Fri, Dec 25, 2009 at 09:35:42PM +0100, Eric Valette wrote:
I had a file system witha date set in the future, and thus entered
single mode. I had then a wrong keyboard
This shouldn't be happening so I need you to make few tests in order to
see what went wrong.
First, to make it clear - I
On 26/12/2009 14:52, Anton Zinoviev wrote:
On Fri, Dec 25, 2009 at 09:35:42PM +0100, Eric Valette wrote:
I had a file system witha date set in the future, and thus entered
single mode. I had then a wrong keyboard
This shouldn't be happening so I need you to make few tests in order to
see
On 26/12/2009 17:04, Eric Valette wrote:
On 26/12/2009 14:52, Anton Zinoviev wrote:
On Fri, Dec 25, 2009 at 09:35:42PM +0100, Eric Valette wrote:
I had a file system witha date set in the future, and thus entered
single mode. I had then a wrong keyboard
This shouldn't be happening so I need
BTW readding the scripts, it look like the bug is more in console-common
and that for some reason, the /etc/console/boottime.kmap.gz does not get
loaded.
I entered rescue mode again and did the loadkeys
/etc/console/boottime.kmap.gz and got my french keyboard back.
Unfortunately I had still
On 26/12/2009 17:39, Eric Valette wrote:
Here are the buggy lines in keymap.sh
# If setupcon is present, then we've been superseded by console-setup.
if type setupcon /dev/null 21; then
exit 0
fi
because console-setup is run tto late in case of voluntary single mode
or failure during
On 26/12/2009 18:11, Eric Valette wrote:
On 26/12/2009 17:39, Eric Valette wrote:
Here are the buggy lines in keymap.sh
# If setupcon is present, then we've been superseded by console-setup.
if type setupcon /dev/null 21; then
exit 0
fi
because console-setup is run tto late in case of
On Sat, Dec 26, 2009 at 06:39:13PM +0100, Eric Valette wrote:
I tested manually after entering the maintenance mode S06keyboard-setup
and yes it does print something and does a setupcon -k but the
keyboard is still wrong after the script has executed.
By wrong do you mean it is a QWERTY
On 26/12/2009 20:16, Anton Zinoviev wrote:
On Sat, Dec 26, 2009 at 06:39:13PM +0100, Eric Valette wrote:
I tested manually after entering the maintenance mode S06keyboard-setup
and yes it does print something and does a setupcon -k but the
keyboard is still wrong after the script has executed.
On Sat, Dec 26, 2009 at 08:30:56PM +0100, Eric Valette wrote:
What happens if you execute
loadkeys /etc/console-setup/cached.kmap.gz
Well I just removed it just in case. I will have to wait until
reboot but I cannot now...
In order to make the test more useful try to recreate this file
I finally found the bug: I traced setupcons -k in error mode and it
expects to find ckbcomp but unfortunately /usr is not mounted and
ckbcomp is /usr/bin/ckbcomp
I traced the setupcons -k with set -x and it exist with doing anyting
because it does not find ckbcomp in the path.
-- eric
Package: console-setup
Version: 1.50
Severity: normal
I had a file system witha date set in the future, and thus entered single mode.
I had
then a wrong keyboard which is annoying because when you are in this mode you
are likely to kill your machine if using the wrong key (even enetring the
15 matches
Mail list logo
