Package: console-tools
Version: 1:0.2.3dbs-65
Severity: minor
Hi,
on my system I have 10 consoles active, but unicode_start fails (or
better: doesn't have any effect) when invoked from a tty higher than 6.
tty1 to tty6 are in use, tty7 is left for X, tty9 to tty12 are in used.
tty8 is left unused because sometimes I redirect logs on that console.
The problem is in the way the upper bound of the iteration to set
unicode mode is computed:
NUM=`fgconsole --next-available`
When invoked from e.g. tty10 and tty8 is not in use `fgconsole
--next-available` returns 8 and of course tty10 is not affected by
unicode_start.
Fix may be as simple as this:
--- unicode_start.orig 2006-10-03 18:09:11.492146500 +0200
+++ unicode_start 2006-10-03 18:09:22.740849500 +0200
@@ -46,8 +46,7 @@
DEVICE_PREFIX="/dev/tty"
fi
-NUM=`fgconsole --next-available`
-NUM=`expr ${NUM} - 1 `
+NUM=`fgconsole`
# This needs a better fix, but because unicode_{start,stop} are called
# before getty starts the other consoles, if only one console set, then
# set for the first 6 VTs, since these are normally started by inittab
but I think that it will break console-screen.sh. Maybe the right "fix"
is to add another script that touches only the _current_ tty?
Luca
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
Versions of packages console-tools depends on:
ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libconsole 1:0.2.3dbs-65 Shared libraries for Linux console
ii lsb-base 3.1-17 Linux Standard Base 3.1 init scrip
Versions of packages console-tools recommends:
ii console-common 0.7.61 Basic infrastructure for text cons
ii console-data 2:1.0-2 Keymaps, fonts, charset maps, fall
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
