Comment 262 for bug 129910

On Fri, Jan 11, 2008 at 09:23:54PM -0000, Paul Dufresne wrote :
> You have to understand that we normally don't fix bugs in a version that was released.

You have to understand that I'm part of MOTU and thus do know what a SRU is,
thanks.

> Only in exceptional case this is done, and the conditions for doing so are described at:
> https://wiki.ubuntu.com/StableReleaseUpdates
>

I see. A non-usable framebuffer for basically evey ubuntu user is actually a
very, very common bug. My mistake

> Among the conditions, the following:
> An explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix; generally, SRUs will not be accepted if the bug has not been fixed in the development branch.
>
> Almost no one have reported this problem on Hardy (I have checked all duplicates, and they are all about Gutsy, except mine: bug #162400, which I am
> not sure is a duplicate, because I have no screen, even without VGA=xxx option, which I seems to be alone in that situation).
>
> Bug importance are described at:
> https://wiki.ubuntu.com/Bugs/Importance
>
> One could argue that it should be low because it has many easy workarounds:
> -don't use vga=xxx

This is for people who are too lazy to apply the fix. Until someone tells
me why I shouldn't use the framebuffer, which is, let's be honest, quite handy
if you want to work properly with your consoles, I see no reason why this would
be a proper fix

> -use the terminal in graphics mode rather than real virtual terminals

Btw, it prevents you from seeing usplash. Just use usplash at the lower res
then, with svgalib. woot.

> -and the one consisting at modifying initramfs modules to load fbcon and vesa
> But as it affects many people, well yes, medium seems fair.
>

Why in hell is that so hard for the kernel team to just comment on the solution,
and possibly tell us why this should or should not be done, and eventually fix
the thing or definitely mark it as a won't fix ?. Oh, wait. I was dreaming.
Nevermind.

> A new alpha version of Hardy have just come out: Alpha 3.
> Please consult http://www.ubuntu.com/testing/ , download alpha 3 CD and test how it works for you with it,
> and report results here.
>
> --
> Blank ttys when using vesafb (vga=xxx)
> https://bugs.launchpad.net/bugs/129910
> You received this bug notification because you are a direct subscriber
> of the bug.

--
Albin Tonnerre, aka Lutin
 - Search a little longer, travel a little further