Re: Bug#383220: CapsShift seems to be ignored by directfb
Christian Perrier a écrit :
The current behaviour fo the fr-latin9 keymap at the Linux console in
unstable is really mad. Just try it, you'll see.
So, it really seems that your proposed fix should be done also for
console use.
I reported this bug against directfb not expecting a fix on that issue
but rather more pointing out that the user should be warned about it.
Since the following is not directly linked to directfb I reply to
383220-quiet@bugs.debian.org and to debian-l10n-french@lists.debian.org,
but I really don't know if I am rigth to do so (if not please accept
apologies).
Some times ago, I stopped using directfb (and therefore the fix i
mentionned in the original bug report). And I never noticed any problems
with the linux console since then (but I don't use it often).
Following Christian 's surprising remark about the fr-latin9 keymap
current behavior at the linux console I checked myself tonigh (I am
using testing):
- the capslock key does not work anymore (it has no effect),
- the proposed fixed (switching Shift and CapsShift on the fly) does not
help with the capslock key,
I gave a test to the latest version of console-data and console-common
(those in unstable) and I also obtained 'mad behaviors'.
So I downgraded back to the testing version but I still had the 'mad
behaviors'. Running dpkg-reconfigure console-data or re-running
/etc/init.d/keymap.sh or /etc/init.d/console-screen.sh did not help.
The only solution was to reboot the system. Everything came back as
expected (except for the capslock key that looks like dead).
But I also observed that if i run '/etc/init.d/keymap.sh reload', the
'mad behaviors' come back (by the way mad behavior here means some keys
no more responding and some other keys responding twice, I don't know if
Christian observed the same).
So to temper Christian's remark:
- following a normal boot, the only 'mad behavior' I can observe with
the fr-latin9 keymap at the linux console is this 'dead' capslock key,
- 'mad behaviors' are observed after a console-data or console-common
upgrade or after running /etc/init.d/keymap.sh reload.
I don't know if this help, but I just wanted to point out that some
people may not notice anything with the linux console (although there
are obviously some problems that may not be related to the CapsShift key).
Regards
Reply to: