Comment 18 for bug 447765

i see this bug confirmed (i can confirm it myself also), but it is assigned to no-one... this means it will probably never get fixed, unless some update from upstream fixes it

should we just wait or try to get someone on the bug team on it?

I'm not sure what is the best course of action with situations like this... and i really miss my high-resolution tty's (especially now when grub2 allows my native 1680+1050...can't wait to try this out)