You have to understand that we normally don't fix bugs in a version that was released. Only in exceptional case this is done, and the conditions for doing so are described at: https://wiki.ubuntu.com/StableReleaseUpdates
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 -use the terminal in graphics mode rather than real virtual terminals -and the one consisting at modifying initramfs modules to load fbcon and vesa But as it affects many people, well yes, medium seems fair. 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 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
