Bug#461956: marked as done (console-setup: issues with <F10>,<F11>,<F12> and dead keys)
Your message dated Fri, 4 Apr 2008 14:13:00 +0200
with message-id <20080404121300.GC13590@freesources.org>
and subject line Re: Bug#461956: console-setup: issues with <F10>,<F11>,<F12> and dead keys
has caused the Debian Bug report #461956,
regarding console-setup: issues with <F10>,<F11>,<F12> and dead keys
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
- To: Debian Bug Tracking System <firstname.lastname@example.org>
- Subject: console-setup: issues with <F10>,<F11>,<F12> and dead keys
- From: Jonas Meurer <email@example.com>
- Date: Mon, 21 Jan 2008 17:45:44 +0100
- Message-id: <20080121164540.GA24356@freesources.org>
Since the upgrade to the last console-setup, my keyboard behaves
different on the console:
- The keys <F10>, <F11> and <F12> don't work anymore, at least I cannot
change to tty10 with <Alt>+<F10> anymore. The only way to reach ttys
higher than tty9 is the use of <Alt>+<Right_Arrow> ...
- The dead keys on my german keyboard behave like dead keys again, even
though I selected "eliminate dead keys". In other words, characters
like ^ ' ` ~ are not printed directly after pressing the key anymore,
but rather are printed just after the following key is pressed. In case
that the following key is a letter with support for the 'dead character'
in some font, like ^ and a, the result is instead of ^a.
After reloading the default keymap (for example via 'dpkg-reconfigure
console-common') everything behaves normal again. If I rerun
'/etc/init.d/console-setup start' afterwards, the issues return.
Please tell me how I can give you additional information for fixing this
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23-2-amd64-resivo
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages console-setup depends on:
ii console-terminus 4.20-6 Fixed-width fonts for fast reading
ii debconf [debconf-2. 1.5.18 Debian configuration management sy
ii xkb-data 1.1~cvs.20080104.1-1 X Keyboard Extension (XKB) configu
Versions of packages console-setup recommends:
ii kbd 1.12-19 Linux console font and keytable ut
-- debconf information:
* console-setup/variant: Germany - Eliminate dead keys
* console-setup/altgr: Right Alt
* console-setup/ttys: /dev/tty[1-9] /dev/tty10 /dev/tty11 /dev/tty12
* console-setup/codeset: # Latin1 and Latin5 - western Europe and Turkic languages
console-setup/toggle: No toggling
* console-setup/fontface: TerminusBold
* console-setup/fontsize-text: 14
* console-setup/compose: No compose key
console-setup/switch: No temporary switch
* console-setup/charmap: UTF-8
* console-setup/layout: Germany
* console-setup/model: Logitech Ultra-X Keyboard
* console-setup/fontsize-fb: 14
--- End Message ---
--- Begin Message ---
On 04/04/2008 Anton Zinoviev wrote:
> On Mon, Jan 21, 2008 at 05:45:44PM +0100, Jonas Meurer wrote:
> > Since the upgrade to the last console-setup, my keyboard behaves
> > different on the console:
> > - The keys <F10>, <F11> and <F12> don't work anymore, at least I cannot
> > change to tty10 with <Alt>+<F10> anymore. The only way to reach ttys
> > higher than tty9 is the use of <Alt>+<Right_Arrow> ...
> > - The dead keys on my german keyboard behave like dead keys again, even
> > though I selected "eliminate dead keys".
> I can only hope that the problem still exists on your system. :)
Unfortunately I just trashed my old system and setup a new one as I just
got a new computer. That's the first time I did this since many many
In other words, I'm not able to reproduce the bug any longer. I use
console-setup again on my new system, but I've another keyboard and the
F10 to F12 keys work like a charm.
I thus close this bugreport, as there's no way to verify its existance
--- End Message ---