[01:14] <scott_ino> I'd like to try and test multi-touch support now, either with existing tools, or new ones. I was looking at Utouch but realize that they're working on new framework
[01:15] <scott_ino> for next release. So I suppose my question is, how can I test multi-touch currently
[06:33] <trinikrono_> i would like to join the xswat can someone help me prepare?
[17:08] <ScottK> Sarvatt: What would be the way to communicate the following to Intel developers in a way that would be constructive and useful (re the ongoing kwin mess):
 mgraesslin: While I'm waiting for kdebase-workspace to compile, it would help a lot if I could get a list of the capabilities Intel is misreporting (or some idea how to figure it out).  Canonical does have people that can talk to Intel if I can tell them what needs to be communicated.
 the list is rather short: we need framebuffer objects and shaders and in inderict rendering mode the unsupported (impossible) extensions should be removed. That's nothing I can provide as that's something only the driver developers can know
[17:16] <ScottK> Additionally:
 ScottK: if they need a reference: https://bugs.kde.org/show_bug.cgi?id=173556#c41
 that's how NVIDIA does it
[17:16] <ubot4> KDE bug 173556 in compositing "Shader support not detected on various systems" [Normal,Resolved: fixed]
[17:21] <penguin42> Any mesa guys here? I've got a bug of mine with a link to a particular patch to be cherry picked from the mesa repos that makes radeon useable on maverick and I wondered what the chances of it getting in are - bug 6269943
[17:21] <ubot4> penguin42: Error: Bug #6269943 not found.
[17:23] <ScottK> penguin42: You might look at the git snapshot in the sarvatt/mesa PPA.  If that solves your problem, then knowing that helps the chances of the mesa update getting in.
[17:23] <penguin42> bug 626943
[17:23] <ubot4> Launchpad bug 626943 in mesa (Ubuntu) "[Maverick] Flickering on Radeon - please cherry pick646d2e9fbc41bf49075013009e9583bec4a51168 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/626943
[17:24] <penguin42> scottk: OK, will do
[17:26] <penguin42> ScottK: Is that just a build from the mesa git head?
[17:26] <ScottK> ~head yes.
[17:26] <ScottK> I think anyway.  It's take Sarvatt to know for sure.
[17:26] <penguin42> ScottK: So I'm fairly sure that will have it since my bug is just asking for a patch in the mesa git to be cherry picked
[17:26] <penguin42> (with a bit of clean up)
[17:27] <ScottK> right, but if you try that package that is specifically working towards an update in Maverick and can say it fixes the problem, that's more credible than "I think the fix is in there".
[17:28] <penguin42> ScottK: I know specifically that the git entry that I reference fixes it since I've got a ppa with that change added
[17:28] <ScottK> Yes, but how about that git commit plus all the other changes?
[17:28] <ScottK> Up to you, anyway.
[17:30] <penguin42> Yeh I can give that set a try; but is the intent in Maverick to do a mesa update generically or just to stick with the version in the beta?
[17:37] <ScottK> The X people intend to update. I don't think they've talked to the release team yet.
[17:37] <penguin42> ok
[21:39] <intrader> I am in the process of filing a bug report and I don't know the package, but suspect Xorg or the kernel (I have forum thread http://ubuntuforums.org/showthread.php?p=9782591#post9782591)
[23:53] <RAOF> Sarvatt: “../../dix/pixmap.c:118: AllocatePixmap: Assertion `pScreen->totalPixmapSize > 0' failed.” means that you've tried to copy create a pixmap before the screen pixmaps have been set up; you can see uxa_init in uxa/uxa.c(I think?) for what they do.