This bug was fixed in the package linux - 2.6.27-14.41
---
linux (2.6.27-14.41) intrepid-proposed; urgency=low
[ Stefan Bader ]
* Revert "SAUCE: input: Blacklist digitizers from joydev.c"
- LP: #300143
linux (2.6.27-14.40) intrepid-proposed; urgency=low
[ Amit Kucheria ]
This bug was fixed in the package linux - 2.6.24-24.56
---
linux (2.6.24-24.56) hardy-proposed; urgency=low
[Stefan Bader]
* Rebuild of 2.6.24-24.54 with 2.6.24-24.55 security release applied
linux (2.6.24-24.54) hardy-proposed; urgency=low
[Andy Whitcroft]
* SAUCE: do not
I have also reproduced this issue with the kernel in intrepid,
2.6.27-14.35, and can confirm that the kernel in intrepid-proposed,
2.6.27-14.36, fixes the issue (though showconsolefont has some
interesting artifacts in both kernels). Marking verification-done.
** Tags added: verification-done
** T
I was able to reproduce this issue with a previous hardy kernel,
2.6.24-23.52, and can confirm that the kernel in hardy-proposed,
2.6.24-24.56, improves the handling of these characters. One issue I did
notice is that the screen blanking due to inactivity doesn't end up
applying to the characters w
Uwe Geuder wrote on 2009-04-20:
". . . the characters previously corrupted appear in a different color
now. While all characters, which worked before are displayed in some
kind of grey, the "new" characters are displayed in white. Any
explanation for this? . . ."
Yes, that is LP:392795.
--
Non
This bug was fixed in the package linux - 2.6.28-13.44
---
linux (2.6.28-13.44) jaunty-proposed; urgency=low
[ Stefan Bader ]
* Revert "SAUCE: [jaunty] ALSA: Add retry for Intel8x0 clock measurement"
* Revert "SAUCE: [jaunty] ALSA: Fix clock and buffer calculations for
Inte
This is very important problem!
I cant work in console because Russian characters are broken.
It is impossible to work with translated programs (eg midnight commander) and
to work with Russian filenames.
Ls command returns list of garbage.
Its looks like characters on intrepid-random-pixel-range.j
Accepted linux into jaunty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
N
This patch was included in the first Karmic upload.
linux (2.6.30-1.1) karmic; urgency=low
* Initial release after rebasing against v2.6.30-rc3
-- Tim GardnerThu, 12 Mar 2009 19:16:07 -0600
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
Non-ASCII characte
Has been committed to Karmic
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: Stefan Bader (stefan-bader-canonical) => Tim Gardner (timg-tpi)
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net
Fix committed to Intrepid (target 2.6.27-14.34)
** Changed in: linux (Ubuntu Intrepid)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Intrepid)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
** Changed in: linux (Ubuntu Jaunty)
Assignee: (unassign
Committed to Hardy (target 2.6.24-24.54)
** Changed in: linux (Ubuntu Hardy)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Hardy)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs
Committed to Jaunty (target 2.6.28-12.43)
** Changed in: linux (Ubuntu Jaunty)
Status: Triaged => Fix Committed
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notification because you are a member of Ubuntu
Bugs, w
Committed to Jaunty (target Ubuntu-2.6.28-12.43)
** Description changed:
+ SRU justification:
+
+ Impact: The use of 512 character fonts on a vga console is broken since
+ seemingly ever until now somebody noticed. While not being a panic spreading
+ issue it can simply be fixed.
+
+ Fix: Let t
** Also affects: linux (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Intrepid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jaunty)
Importance: Undecided => Low
** Changed in: linux (Ubuntu Jaunty)
Status: New =>
OK, so please feel free to add my email as tested-by.
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
> However, if this somehow includes the promise that this does not cause
> any regression, I would not feel comfortable to make such promise after
> such little usage and with my non-existing backgound knowledge about the
> involved code.
I double checked, this only means you looked at the proble
IMO it can only cover that it fixed the issue for you. But I ask someone else
to be safer.
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Forgot to answer...
> would it be ok to add you with your email as a "Tested-by"
I'm not familiar with LKML policies and I couldn't find anything in the
FAQ at least quickly. If looking at some characters on the console can
be considered testing in that context, it's OK to add my email.
However,
> The man page is correct and it _will_ only affect the last 256 glyphs.
You are right, I didn't read it carefully enough and understood it
wrong.
> The trick is to mirror the colours indexed by 0-7 to the ones indexed
by 8-15.
If this were possible it would be another bug, because it does clear
> No character corruption occurs anymore in my sampletable.txt in tty1 ...
> tty6. Correct characters seem to be displayed all the time. (Well I have
> not double checked every single character with a Unicode table. But
> those characters I happen to know by heart are correct and all other
> look
Oops, broken link in previous comment. New attempt:
https://bugs.launchpad.net/bugs/303561
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the intrepid versions. I've just tested the i386 version in
the same machine as this report was created (see attached files above).
No character corruption occurs anymore in my sampletable.txt in tty1 ...
tty6. Correct characters seem to be displayed all the time. (Well I have
not doubl
Uwe Geuder wrote:
> Hmm, your kernels are for Jaunty. I have only Hardy and Intrepid
Maybe simpler: I added Intrepid kernels (based on proposed) to the same
place.
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notificati
Hmm, your kernels are for Jaunty. I have only Hardy and Intrepid
systems. I have reproduced the problem in Jaunty by using the live CD.
But I guess I cannot update the kernel when using the live CD, can I?
I can probably install a Jaunty to some disk corner, but I might take a
couple of days or we
Gosh, I think I found the little bugger. It seems this has been that way near
forever but probably did not always matter (as long as your font only has 256
characters). The problem lies in the function that returns the font data of a
vga console. It will only write back the first 256 characters
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.
Oops, couldn't read my own handwritten notes and the previous comment
got wrong...
These 2 reports might contain duplicate aspects (but also some other
things)
https://launchpad.net/bugs/273189
https://launchpad.net/bugs/303561
This one sounds somehow loosely related to the topic (but not a
dupl
There are 2 more reports, which I originally thought they report the
same issue. However, after reading them again, I decided not to mark
them as duplicates, because they contain also other aspects, which might
be unique to them. For cross reference, the links are
https://launchpad.net/bugs/190746
** Attachment added: "jaunty-liveCD.jpg"
http://launchpadlibrarian.net/24802562/jaunty-liveCD.jpg
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Oops launchpad does not really display the file name.
Picture 1/4 was intrepid-no-accents.jpg
Picture 2/4 was intrepid-random-pixel-range.jpg
** Attachment added: "intrepid-single-user-OK.jpg"
http://launchpadlibrarian.net/24802539/intrepid-single-user-OK.jpg
--
Non-ASCII characters get corr
** Attachment added: "sampletable.txt for easy reproduction"
http://launchpadlibrarian.net/24802397/sampletable.txt
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "picture 2/4"
http://launchpadlibrarian.net/24802480/intrepid-random-pixel-range.jpg
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "my /etc/defaults/console-setup"
http://launchpadlibrarian.net/24802358/console-setup
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24802359/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24802360/CurrentDmes
** Attachment added: "picture 1/4"
http://launchpadlibrarian.net/24802446/intrepid-no-accents.jpg
--
Non-ASCII characters get corrupted in framebuffer console
https://bugs.launchpad.net/bugs/355057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
35 matches
Mail list logo