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 o
** 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-
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 WatsonThu, 27 Nov 2008 19:00:39 +
** Chang
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.
--
u
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 a
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 accurate
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 #27
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 o
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 WatsonThu, 27 Nov 2008 19:07:15 +
** Ch
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
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 Ubun
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
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, u
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
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
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
** 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
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 +000
** 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
** 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
- k
20 matches
Mail list logo
