[Bug 130444] Re: Characters incorrectly echoed to virtual terminal screens

2008-04-30 Thread Axel Harvey
This is most disturbing. I already skipped upgrading from 7.04 to 7.10
because I believed the problem would be fixed in 8.04 (see Colin
Watson's notes above). Is there likely to be a patch or add-on fix soon
so I can move on to Hardy Heron?

-- 
Characters incorrectly echoed to virtual terminal screens
https://bugs.launchpad.net/bugs/130444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 130444] Re: Characters incorrectly echoed to virtual terminal screens

2007-11-02 Thread Axel Harvey
UPDATE  Another possible clue? --  Context is Ubuntu Feisty Fawn. This was 
discovered accidentally. When the grub boot starts, just after the Ubuntu logo 
appears on the screen but before the sign-in box comes up, I do ctrl-alt-F1 and 
switch to TTY display (with all the messages that are usually hidden at boot 
time). After a few seconds the normal character set changes to a slightly 
uglier one -- looking like something circa 1980 -- and a little while later the 
display returns by itself to gui mode and I can sign in as usual, as if I had 
never left the gui terminal. 
 
Now I return to a TTY virtual terminal with the slightly primitive character 
set, and lo! *all the accents appear in their proper places*. There are a few 
minor discrepancies, the only major one being that é appears as £, but believe 
me I am much, much happier with the new arrangement; and Midnight Commander 
now shows up with proper borders. If I write a file in TTY and then read it in 
gui, the £ will show as é.
 
Three more points: (1) all virtual terminals are affected the same way; (2) the 
caps lock now works; (3) the output of  stty -a  is the same with this new 
arrangement as it was with the standard arrangement.
 
I must add I am somewhat disconcerted that the importance of this bug has not 
yet been determined. Even if VTs are used only for writing code, there are some 
people who might occasionally write comments in languages other than English (a 
peculiar Indo-European dialect which tries to dispense with accents). Also any 
display that requires borders, such as Midnight Commander, looked terrible on 
the standard VT arrangement; with my accidentally found fix I can now enjoy 
it in its former beauty.

-- 
Characters incorrectly echoed to virtual terminal screens
https://bugs.launchpad.net/bugs/130444
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 130444] Re: Characters incorrectly echoed to virtual terminal screens

2007-08-25 Thread Axel Harvey
I have just noticed that the caps lock key does not work in the virtual
terminals: characters continue to appear as lower-case even when the
Caps pilot light is on. The caps lock works properly with the gui
terminal. The ordinary shift key works properly in both environments. I
don't know if this is relevant information but am offering it as a
possible clue.

-- 
Characters incorrectly echoed to virtual terminal screens
https://bugs.launchpad.net/bugs/130444
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 13938] Re: Entering é character in full name during installation fails

2007-08-15 Thread Axel Harvey
I wonder if this is related to item 130444 Characters incorrectly
echoed to virtual terminal screens [Feisty].

-- 
Entering é character in full name during installation fails
https://bugs.launchpad.net/bugs/13938
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 130444] Characters incorrectly echoed to virtual terminal screens

2007-08-04 Thread Axel Harvey
Public bug reported:

This is a continuation of Bug #19487 and Bug #29523, but since it seems
(at least in Feisty Faun) to involve echoing to screen rather than the
keyboard, I thought I should post it as a separate item.

Following previous discussions, I tried  locale-gen fr_CA  and rebooted,
but the problem did not go away. Incidentally, the system told me it was
generating  fr_CA.ISO-8859-1  but this entity was nowhere to be found
even after I had updated the database.

Therefore I am repeating the note I sent to answers.launchpad.net/ubuntu
, with the added remark that a fix is urgently needed as no civilized
person can get along without using the occasional Umlaut, cedilla, or
tilde.

[ Repeat from answers:]

There is a problem with the echoing of characters to the screen when in
tty (virtual terminal) mode. At first I thought this was related to
fonts in general, but apparently it is not. A brief discussion can be
read in the user forum:

http://ubuntuforums.org/showthread.php?t=512717

The environment: Feisty Fawn with kernel 2.6.20-16-generic #2 SMP. I don't 
remember how the terminal font was selected upon installation, but on checking 
the Language Support menu it appears that I checked English and French, and 
specified English (Canada) as the default language. I also checked Enable 
support to enter complex characters. In the Keyboard Preferences
menu, the keyboard model is Generic 105-key (intl) PC and the layout is 
Canada French (legacy): but I doubt the keyboard layout is relevant here in 
view of the fact that everything works in GUI mode.

For example, in tty the e-acute key (é) is echoed as a blank space on the 
screen. If I type it to a text file I cannot see it; but on
reading the same file with a terminal in GUI mode, the character é is displayed 
properly. The same is true of all characters. Thus the font of the tty virtual 
terminals is identical to that of the GUI terminal. The problem is with echoing 
to the screen.

The following is the arrangement of the four rows of characters as I see
them on the GUI terminal (it is possible that you might not see them the
same way). For each now, alt-keys are listed on the top sub-row; shift-
keys on the middle sub-row; lowercase-keys on the bottom sub-row: The
explanatory notes are not necessarily exhaustive.

¬ ¹ @ ³ ¼ ½ ¾ { [ ] } | [1] [2]
° !  # $ % ?  * ( ) _ + À -- the last character is capital A-grave
° 1 2 3 4 5 6 7 8 9 0 - = à -- the last character is l.c. a-grave

q w e ¶ t ¥ u i ø þ ° [3]
Q W E R T Y U I O P [4] Ç -- the last character is capital C-cedilla
q w e r t y u i o p [4] ç -- the last character is l.c. c-cedilla

æ ß ð ª g h j k l [5] {
A S D F G H J K L : È -- the last character is capital E-grave
a s d f g h j k l ; è -- the last character is l.c. e-grave

\ « » ¢ v b n µ   / -- 2nd and 3rd characters are guillemets
Ù Z X C V B N M ' . É -- the last character is capital E-acute
ù z x c v b n m , . é -- the last character is l.c. e-acute

NOTES:

[1] In GUI: dead key for French ç or Turkish ş.
On tty: all different.
[2] In GUI: dead key for accent sloping up to the left, e.g. ò.
On tty: all different.
[3] In GUI: dead key for tilde; follow with a space to get ~.
On tty: alt + space makes ~; other combinations are different.
[4] In GUI: dead key for circumflex; follow with a space to get ^.
On tty: makes ^ with space; other combinations are different.
[5] In GUI: dead key for accent sloping up to the right, e.g. í.
On tty: all different.

For all but the ordinary, unaccented characters, the virtual terminal
screen echoes what seem to be IBM Code Page 437 characters. The
following is what I see in tty mode. The quote marks surround code
numbers corresponding to the Code Page 437 glyphs (as best I could
identify them) that resemble what I see. The word same indicates that
I see the same things in tty and GUI modes; the number preceeding same
indicates how many characters in a row (horizontally) are the same in
both modes - e.g., q, w, and e in the 2nd row with alt are the
same in both modes, therefore 3same is noted. A question mark ?
indicates that I couldn't be sure of the character code or that the
result varied when a dead key was used with different letters.

TOP ROW, ALT
202, 211, 1same, 205, 214, 215, 216, 5same, ?, ?
TOP ROW, SHIFT
176, 12same, 218
TOP ROW, L.C.
176, 12same, 248

2ND ROW, ALT
3same, 208, 1same, 005, 2same, 015, 021, 176, see [3]
2ND ROW, SHIFT
10same, see [4], 224
2ND ROW, L.C.
10same, see [4], 223 ?

3RD ROW, ALT
?, 247, ?, 190, 5same, ?, 1same
3RD ROW, SHIFT
10same, 225
3RD ROW, L.C.
10same, blank

4TH ROW, ALT
1same, 191, 213, 004, 3same, 207, 3same
4TH ROW, SHIFT
242, 9same, 226
016, 9same, blank

What I think should happen, of course, is that I would see the same
things in tty mode as on the GUI terminal.

** Affects: Ubuntu
 Importance: Undecided
 Status: New

-- 
Characters incorrectly echoed to virtual terminal screens
https://bugs.launchpad.net/bugs/130444