today was busy. but it seems i got nothing "real" done. phone calls, emails, prep work for 4.x and some time spent with the p-man. but very little code. blarg. i'm not sure if it's exactly healthy to measure my life in terms of lines of code, but there you go.
we've got a nasty bug in plasma that's showing itself with intel chipsets and the new xrandr which allows for hot plug monitors. essentially the driver lies to us and says that the newly plugged monitor and the existing one (e.g. the built in lcd on the laptop) are both at (0, 0). so plasma happily puts two desktops there, which leads to neat overlapping desktops. and by neat i meant "what a horrid bug".
i wrote to Keith Packard about it and his reply was essentially that it's up to me to find some way to work around it because he can't guarantee the position or order of monitors at runtime, though i find it hard to believe that even the driver itself doesn't know at *some* point, especially ones both are actually advertised as displaying content. apparently Keith and friends consider this interesting behaviour "par for the course" and expected. i'm disappointed, and i'm not the only one given what i've heard from others working on other projects who are dealing with this same issue. so much for sane software, right? not sure how i'm going to hack around this.
i filed a bug against gtk+ and their argb problems. the gtk+ people have said that they don't accept that the code in plasma is "valid" even though it works with every other toolkit out there. nothing like sluffing off your crashers with "well, you shouldn't do that anyways!" in any case, frederikh came up with a small patch for x.org that could prevent this being a problem for anyone, which is probably an even nicer approach since it fixes things lower in the stack rather having to rely on the good sense of the larger number of people writing code higher up.
good news, however: i got email from nvidia today (hi Ignacio!) letting me know that the argb bug has been fixed. the next driver release will contain the fix, and they'll be letting me know when that comes out so i can help point people with these issues to it.
interesting that the open source projects are less responsive when dealing with on this matter.
in other news, i'm supposed to be doing an interview over skype with the linux action show boys any minute now to talk about the rc1 debacle and kde4 in general ... i've settled back with a glass of wolf blass '04 unwooded chardonay and some cheese and crackers to get in the mood. p is asleep and the house is quiet and warm and clean.
i hope all of you have an excellent weekend. =)