Package: console-tools
Version: 0.2.3dbs-70
Tags: patch
The bug is in debian/patches/260_kernel26fix.patch, in this hunk:
diff -ruN console-tools-0.2.3-old/kbdtools/dumpkeys.c
console-tools-0.2.3/kbdtools/dumpkeys.c
--- console-tools-0.2.3-old/kbdtools/getkeycodes.c 2004-06-26
11:53:20.000000000 +0100
+++ console-tools-0.2.3/kbdtools/getkeycodes.c 2004-06-26 11:53:20.000000000
+0100
@@ -52,7 +74,7 @@
printf("\ne0 %02x: ", sc-128);
}
- if (sc <= 88)
+ if (sc <= sc0)
{
printf(" %3d", sc);
continue;
This prints the identity map for characters up to and includeing sc0.
However, sc0 is the first character for which the mapping is NOT
the identity.
The comparison should be "< sc0".
Demonstration of bug:
I have scancode 29 (left control) remapped. I don't *want* it remapped,
and figuring out who's remapping it is the bug I was working on when this
bug interfered, but that's a different story. Anyway, getkeycodes starts
out saying that the identity map stops at 0x1c, but displays 0x1d -> 29.
If I actually set that explicitly, then it announces an identity map up
to 0x53 -> 83, but now displays 0x54 -> 84, rather than -> 203.
[503]# getkeycodes ; setkeycodes 1d 29 ; getkeycodes
Plain scancodes xx (hex) versus keycodes (dec)
for 1-28 (0x01-0x1c) scancode equals keycode
0x18: 24 25 26 27 28 29 30 31
0x20: 32 33 34 35 36 37 38 39
0x28: 40 41 42 43 44 45 46 47
0x30: 48 49 50 51 52 53 54 55
0x38: 56 57 58 59 60 61 62 63
0x40: 64 65 66 67 68 69 70 71
0x48: 72 73 74 75 76 77 78 79
0x50: 80 81 82 83 203 0 86 87
0x58: 88 117 0 0 95 183 184 185
0x60: 0 0 0 0 0 0 0 0
0x68: 0 0 0 0 0 0 0 0
0x70: 93 0 0 89 0 0 85 91
0x78: 90 92 0 94 0 124 121 0
Escaped scancodes e0 xx (hex)
e0 00: 0 0 0 148 0 0 167 0
e0 08: 0 0 148 0 213 0 226 0
e0 10: 165 0 0 0 211 0 0 0
e0 18: 161 163 0 0 96 97 0 0
e0 20: 113 140 164 150 166 0 358 0
e0 28: 0 0 255 0 0 0 114 0
e0 30: 115 138 172 0 0 98 255 99
e0 38: 100 0 0 0 0 0 0 0
e0 40: 0 0 0 0 0 119 119 102
e0 48: 103 104 0 105 112 106 118 107
e0 50: 108 109 110 111 0 0 0 0
e0 58: 0 0 0 125 126 127 116 142
e0 60: 0 0 0 143 0 217 156 173
e0 68: 128 159 158 157 155 226 0 112
e0 70: 0 0 0 0 0 0 0 0
e0 78: 0 0 0 0 0 0 0 0
Plain scancodes xx (hex) versus keycodes (dec)
for 1-83 (0x01-0x53) scancode equals keycode
0x50: 80 81 82 83 84 0 86 87
0x58: 88 117 0 0 95 183 184 185
0x60: 0 0 0 0 0 0 0 0
0x68: 0 0 0 0 0 0 0 0
0x70: 93 0 0 89 0 0 85 91
0x78: 90 92 0 94 0 124 121 0
Escaped scancodes e0 xx (hex)
e0 00: 0 0 0 148 0 0 167 0
e0 08: 0 0 148 0 213 0 226 0
e0 10: 165 0 0 0 211 0 0 0
e0 18: 161 163 0 0 96 97 0 0
e0 20: 113 140 164 150 166 0 358 0
e0 28: 0 0 255 0 0 0 114 0
e0 30: 115 138 172 0 0 98 255 99
e0 38: 100 0 0 0 0 0 0 0
e0 40: 0 0 0 0 0 119 119 102
e0 48: 103 104 0 105 112 106 118 107
e0 50: 108 109 110 111 0 0 0 0
e0 58: 0 0 0 125 126 127 116 142
e0 60: 0 0 0 143 0 217 156 173
e0 68: 128 159 158 157 155 226 0 112
e0 70: 0 0 0 0 0 0 0 0
e0 78: 0 0 0 0 0 0 0 0
As a meta-question, I notice that console-tools has an impressive number
of very old bugs, some marked "pending upload", and no release activity
or mainainer comments on oncoming bugs since February 2011.
Is there is fact an active maintainer?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
