[00:58] <rick_> johanbr: Thanks.  I'll try that.  
[09:55] <Method> i'm trying to add a patch to the kernel package but can't figure out how the kernel package works, how do i get a real source package rather than the linux_meta package?
[12:49] <thoreauputic> Re: Bug 129910  Yes, I know it is supposedly fixed... Could some kind kernel developer try booting with vga=xxx then attempt to switch from tty1 to any other tty ? Seriously. It might no longer be a kernel problem, and I'm probably off-topic, so apologies. Whatever it is , it isn't fixed (yet)
[12:49] <ubotu> Launchpad bug 129910 in linux "Blank ttys when using vesafb (vga=xxx)" [Medium,Fix released] https://launchpad.net/bugs/129910
[12:51] <thoreauputic> Tested repeatedly both on live Beta hardy CD and using an install without X. Bug comments also indicate the problem exists on a beta server install.
[12:54] <mjg59> thoreauputic: No, that sounds like an entirely different bug
[12:55] <thoreauputic> mjg59: I have reported a bug against console-setup - do you think that might be it?
[12:55] <mjg59> No, it's the kernel
[12:55] <thoreauputic> ah
[12:56] <mjg59> It's just not bug 129910
[12:56] <ubotu> Launchpad bug 129910 in linux "Blank ttys when using vesafb (vga=xxx)" [Medium,Fix released] https://launchpad.net/bugs/129910
[12:56] <thoreauputic> OK
[12:56] <thoreauputic> well, typing "setupcon" blindly resores the tty
[12:56] <thoreauputic> *restores
[12:56] <mjg59> Yes, the font is getting lost
[12:56] <thoreauputic> aha
[12:56] <thoreauputic> so this is known ?
[12:57] <mjg59> It's been seen on other framebuffers
[12:57] <mjg59> I wasn't sure it hit vesafb
[12:57] <thoreauputic> it does
[12:57] <thoreauputic> It's a show stopper for me as I am trying to make an up-to-date live CD without X
[12:58] <thoreauputic> it would also be a problem for server admins I imagine
[13:00] <thoreauputic> mjg59: Since this is an LTS relase, I would think it would be nice to fix it before April :)
[13:00] <thoreauputic> ..if possible
[13:00] <mjg59> Yeah
[13:01] <thoreauputic> Lots of unhappy noisy commentators, including me ;)
[13:01] <mjg59> Well, it's still not bug 129910
[13:01] <ubotu> Launchpad bug 129910 in linux "Blank ttys when using vesafb (vga=xxx)" [Medium,Fix released] https://launchpad.net/bugs/129910
[13:01] <thoreauputic> right
[13:02] <mjg59> It'll be 201591
[13:02] <thoreauputic> looking
[13:04] <thoreauputic> yeah that looks more like it
[13:07] <kraut> moin
[13:07] <thoreauputic> mjg59: do you think I should confirm that with vesafb ? Looks like there is at least awareness of the issue
[13:08] <mjg59> Sure
[13:08] <mjg59> And feel free to mark the radeonfb one a dupe of it
[13:08] <thoreauputic> OK I'll append a brief "Confirmed using vesafb"
[13:15] <thoreauputic> mjg59: thanks, done. Hope the fix happens soon :)
[13:57] <cradek> mjg59: bug 204319 has a patch, was triaged and assigned, was the one that got marked duplicate.  Does this affect the assignment?  I see the remaining one is unassigned and "undecided".  I don't care what number it is, but I worked hard to narrow down the breakage to that commit, and I don't want that information to be lost.  Should I also add it to the remaining bug 201591?
[13:57] <ubotu> Launchpad bug 204319 in linux "radeonfb regression: disappearing fonts upon VT switch (dup-of: 201591)" [Medium,Triaged] https://launchpad.net/bugs/204319
[13:57] <ubotu> Launchpad bug 201591 in linux "atyfb regression - screen blank except for blinking cursor after fbcon vtswitch " [Undecided,Confirmed] https://launchpad.net/bugs/201591
[13:59] <mjg59> cradek: It doesn't have a patch
[14:03] <cradek> true I misspoke.  It does say which 10 line commit broke the framebuffers though.  the remaining bug 201591 does not have that very useful information
[14:03] <ubotu> Launchpad bug 201591 in linux "atyfb regression - screen blank except for blinking cursor after fbcon vtswitch " [Undecided,Confirmed] https://launchpad.net/bugs/201591
[14:04] <mjg59> cradek: I'm working on it now
[14:04] <cradek> thank you
[14:05] <mjg59> Ah, I think I see the problem
[14:09] <mjg59> Possible
[14:10] <cradek> I wish the commit message had said which X drivers required this fix -- hard to check it without knowing that
[14:10] <cradek> it's trivial to just fix the consoles [by removing this commit]
[14:11] <mjg59> No, that breaks other stuff
[14:11] <cradek> yes I understand that
[14:12] <mjg59> It fixes that specific aspect of the consoles, and breaks another :)
[17:58] <mjg59> cradek: Ok, think I've fixed it
[18:15] <cradek> mjg59: thanks! I will be able to test it tomorrow US daytime