[Bug 130444] Re: Console not correctly set up after boot
I don't know if my problem is the same because Jaunty and karmic worked for me. Would someone look at bug 528769 and tell me if it is a duplicate or not? -- Console not correctly set up after boot 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: Console not correctly set up after boot
OK, thanks. I think this is an essentially unrelated bug, much closer to bug 273189 than to this one. -- Console not correctly set up after boot 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: Console not correctly set up after boot
** Tags added: verification-done ** Tags removed: verification-needed -- Console not correctly set up after boot 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: Console not correctly set up after boot
This bug was fixed in the package console-setup - 1.21ubuntu9 --- console-setup (1.21ubuntu9) hardy-proposed; urgency=low * Create /dev/tty[1-6] in our initramfs script before trying to operate on them (LP: #130444). -- Colin Watson cjwat...@ubuntu.com Thu, 27 Nov 2008 19:00:39 + ** Changed in: console-setup (Ubuntu Hardy) Status: Fix Committed = Fix Released -- Console not correctly set up after boot 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: Console not correctly set up after boot
Can you type the locale-specific characters at something like 'cat /dev/null' (as opposed to a login or shell prompt)? If so, I think that is likely to be a different bug (indeed, bug 273189 is definitely distinct from this one). This bug is fixed if the characters can be typed and appear accurately at 'cat /dev/null'. -- Console not correctly set up after boot 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: Console not correctly set up after boot
Yes after logging in there is no problem in both the shell prompt and the cat. But strangely, the login prompt does not work now. non-ascii characters are not displayed *at all*. And backspace does not delete the login prompt. I'm not sure what caused this, the machine was not updated. There was an update to 'login' package, I installed it but still non- ascii chars are not printed at login prompt only -- Console not correctly set up after boot 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: Console not correctly set up after boot
I tested on hardy and the bug is still partially present. First of all a tip to other users; I purged console-setup to get rid of my previous tries on keymap.gz and etc.. Reinstalled again from hardy- proposed. I have previously removed -8 from getty parameters at /etc/event.d/ttyX files at #273189, I put them back. running dpkg-reconfigure console-setup and rebooting made the characters appear. The remaining part of the problem is; after typing locale specific characters (çöğüş) backspace key deletes the prompt text. It is narrated in detail at #273189 This is not a very big deal but it's still a bug I think :) Is it present in intrepid or jaunty, can anyone test ? -- Console not correctly set up after boot 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: Console not correctly set up after boot
This bug was fixed in the package console-setup - 1.25ubuntu4 --- console-setup (1.25ubuntu4) intrepid-proposed; urgency=low * Create /dev/tty[1-6] in our initramfs script before trying to operate on them (LP: #130444). -- Colin Watson cjwat...@ubuntu.com Thu, 27 Nov 2008 19:07:15 + ** Changed in: console-setup (Ubuntu Intrepid) Status: Fix Committed = Fix Released -- Console not correctly set up after boot 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: Console not correctly set up after boot
Resetting verification tag for hardy. Can anyone please test the update on Hardy? ** Tags added: verification-needed ** Tags removed: verification-done -- Console not correctly set up after boot 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: Console not correctly set up after boot
No regressions for me with the intrepid update, considering verified for intrepid. Still needs feedback for Hardy. ** Changed in: console-setup (Ubuntu Gutsy) Status: New = Won't Fix ** Tags added: verification-done ** Tags removed: verification-needed -- Console not correctly set up after boot 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
Re: [Bug 130444] Re: Console not correctly set up after boot
Will there be a backport for Intrepid ? On Wed, Nov 26, 2008 at 12:30:06PM -, Launchpad Bug Tracker wrote: This bug was fixed in the package console-setup - 1.28ubuntu3 ---end quoted text--- -- Console not correctly set up after boot 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: Console not correctly set up after boot
Yes, that's why I targeted the bug at Intrepid - though I'm about to go on holiday and may not get to it until I get back. ** Description changed: This is a long-running problem with several different incarnations. Bug 91422 was caused by the splash screen forgetting to save and restore the console font when switching to and from graphics mode, fixed in Ubuntu 7.10. In https://blueprints.launchpad.net/ubuntu/+spec/hardy-console, we proposed a fix in the kernel which would deal with this problem centrally rather than having to fix every single X driver individually, and this was fixed in Ubuntu 8.04. However, Ubuntu 8.10 and Jaunty still exhibit similar symptoms, so I'm grabbing this bug to serve as a sink for duplicates. At the moment, the console is not set up correctly because /dev/tty1, /dev/tty2, etc. do not exist at the point when console-setup's initramfs script tries to deal with this. The simple fix is to have it create those devices itself, and once I do this I find that the console is set up correctly. I think we should backport this fix at least to hardy and intrepid, and possibly gutsy as well; I see no downside in doing so. + DEVELOPMENT BRANCH: Fixed in console-setup 1.28ubuntu3. + + PATCH: http://bazaar.launchpad.net/~ubuntu-core-dev/console- + setup/ubuntu/revision/86 + TEST CASE: Install in Georgian (to pick a language where it's fairly obvious), and switch to Ctrl-Alt-F1 after installation. Confirm that you can type Georgian letters and that they display as something that actually looks like letters rather than blank spaces or obvious visual corruption. -- Console not correctly set up after boot 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: Console not correctly set up after boot
I've uploaded backports of this fix to gutsy-proposed, hardy-proposed, and intrepid-proposed. I'd appreciate it if somebody else in ubuntu-sru could review them. -- Console not correctly set up after boot 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: Console not correctly set up after boot
While the patch itself is pretty obvious and trivial, it's impact is much less so, and could uncover other problems. With hardy being LTS, it does make sense to backport it there, and we can probably find some testers there. But since the underpinnings changed in every release (kernel fix, usplash save/restore), we can't just translate hardy/intrepid verification results to gutsy. Since gutsy is fairly old already, and only has 4 months to live, by now people either learned to live with that problem, or use something else. I'm also okay with intrepid, since we currently have lots of people using intrepid-proposed. ** Changed in: console-setup (Ubuntu Intrepid) Status: New = Fix Committed ** Tags added: verification-needed -- Console not correctly set up after boot 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: Console not correctly set up after boot
I don't mind about gutsy personally; it was really just collect-the-set since the patch backported trivially. I've put the fixed package for gutsy in my PPA: deb http://ppa.launchpad.net/kamion/ubuntu gutsy main -- Console not correctly set up after boot 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
Re: [Bug 130444] Re: Console not correctly set up after boot
Hello, I installed console-setup 1.28ubuntu3 from Jaunty on my Intrepid, and the bug got fixed). Thanks ! -- Console not correctly set up after boot 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: Console not correctly set up after boot
** Summary changed:
- Characters incorrectly echoed to virtual terminal screens
+ Console not correctly set up after boot
** Description changed:
- 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.
+ This is a long-running problem with several different incarnations. Bug
+ 91422 was caused by the splash screen forgetting to save and restore the
+ console font when switching to and from graphics mode, fixed in Ubuntu
+ 7.10. In https://blueprints.launchpad.net/ubuntu/+spec/hardy-console, we
+ proposed a fix in the kernel which would deal with this problem
+ centrally rather than having to fix every single X driver individually,
+ and this was fixed in Ubuntu 8.04. However, Ubuntu 8.10 and Jaunty still
+ exhibit similar symptoms, so I'm grabbing this bug to serve as a sink
+ for duplicates.
- 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.
+ At the moment, the console is not set up correctly because /dev/tty1,
+ /dev/tty2, etc. do not exist at the point when console-setup's initramfs
+ script tries to deal with this. The simple fix is to have it create
+ those devices itself, and once I do this I find that the console is set
+ up correctly.
- 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.
+ I think we should backport this fix at least to hardy and intrepid, and
+ possibly gutsy as well; I see no downside in doing so.
- [ 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
[Bug 130444] Re: Console not correctly set up after boot
** Changed in: console-setup (Ubuntu) Status: Triaged = Fix Committed -- Console not correctly set up after boot 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: Console not correctly set up after boot
** Changed in: console-setup (Ubuntu Hardy) Importance: Undecided = High Assignee: (unassigned) = Colin Watson (kamion) Status: New = Triaged Target: None = ubuntu-8.04.2 -- Console not correctly set up after boot 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: Console not correctly set up after boot
This bug was fixed in the package console-setup - 1.28ubuntu3 --- console-setup (1.28ubuntu3) jaunty; urgency=low * Create /dev/tty[1-6] in our initramfs script before trying to operate on them (LP: #130444). -- Colin Watson [EMAIL PROTECTED] Wed, 26 Nov 2008 12:15:12 + ** Changed in: console-setup (Ubuntu) Status: Fix Committed = Fix Released -- Console not correctly set up after boot 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
