[08:07] <tjaalton> someone complains that libdrm in x-updates "broke multiarch"
[08:08] <tjaalton> fails to install both amd/i386 versions
[08:08] <tjaalton> or upgrade in this case
[08:12] <bryce> hrm
[08:13] <tjaalton> which sounds really weird though
[08:13] <tjaalton> it's been M-A: same for ages
[08:14] <bryce> tjaalton, looks like that was a sync from debian git; is it missing some necessary multi arch patch or something?
[08:14] <tjaalton> I'll forward it to ubuntu-x
[08:14] <tjaalton> no, quantal is fine
[08:14] <tjaalton> *it's fine on quantal, no reason why it wouldn't be on precise
[08:14] <tjaalton> unless there's some apt/dpkg bug
[08:14] <tjaalton> unfixed
[08:15] <yofel_> tjaalton: that mail was from me, need some more info?
[08:15] <tjaalton> yofel: ah right
[08:16] <tjaalton> was about to forward it to ubuntu-x@
[08:19] <tjaalton> yofel: anyway, no reason why it wouldn't upgrade just fine
[08:19] <tjaalton> nothing wrong in the package
[08:19] <tjaalton> source package
[08:20] <yofel> well, the only thing I could think of would be gzip putting out different data on i386 and amd64...
[08:20] <tjaalton> yes
[08:38] <yofel> tjaalton: nvm, downloading the debs straight from launchpad installing them with dpkg worked now. Seems like the amd64 deb wasn't downloaded right. (Except that dpkg didn't notice that)
[08:38] <tjaalton> yofel: ah, yeah I think there's a dpkg bug for that
[08:38] <yofel> ok, thanks anyway :)
[08:39] <tjaalton> np
[10:53] <mlankhorst> ok burning a quantal cd
[10:57] <seb128> mlankhorst, waouh, some people still do that in the age of USB sticks? ;-)
[10:57] <mlankhorst> seb128: didn't want to look into how to make a quantal netboot cd..
[11:01] <mlankhorst> I have 4 netboot filesystems for testing instead
[11:16] <mlankhorst> of course simply right clicking iso and hitting burn fails on size estimation..
[11:30] <mlankhorst> oh now it works, might have been failing on my custom kernel
[13:13] <mdeslaur> any ETA on releasing the mesa packages in precise-proposed and oneiric-proposed? We'd like to publish a security update, and are waiting for those two to go to -updates first...
[13:33] <mlankhorst> seb128: well can reproduce it at least, how silly
[13:34] <seb128> mlankhorst, which one? the xrestop issue?
[13:34] <tjaalton> mdeslaur: bryce has been working on the precise update
[13:35] <mlankhorst> nah the quantal crash
[13:35] <mlankhorst> I'll try with valgrind next
[13:35] <seb128> mlankhorst, oh, ok ;-)
[13:35] <tjaalton> what quantal crash?
[13:35] <mlankhorst> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1065113
[13:36] <tjaalton> ah
[13:41] <tjaalton> mdeslaur: not sure about oneiric
[13:42] <tjaalton> mdeslaur: meh, don't think anyone cares about oneiric anymore, so I guess you can override the current version there and drop the commit
[13:43] <tjaalton> been nearly three months without a verification
[13:45] <mdeslaur> tjaalton: ok, thanks...for precise, I'll wait for bryce to give me an update
[13:55] <mlankhorst> hmmz
[13:56] <mlankhorst> now I have a zero width window for quitting installation
[14:02] <mlankhorst> and other fun
[14:04] <stefan``> hi guys - i'll probably be the 1000s person to annoy you with that
[14:04] <stefan``> ... but any news on bugs 1061073 or 1065125?
[14:06] <mlankhorst> but I did find some suspicious valgrind errors about that, which might explain why it was zero-width too
[16:08] <ScottK> Dear Ubuntu X people: Any suggestions on how to reply to https://lists.ubuntu.com/archives/kubuntu-devel/2012-October/006446.html
[16:09] <tjaalton> try gles
[16:32] <Sarvatt> ScottK, stefan``: was kde-workspace upgrading from 4.9 to 4.9.2 in the same timeframe ruled out? we've had mesa 9.0 snapshots going in for a few months and didn't have any reports of problems also, perhaps testing some of those to locate where the regression introduced might be helpful if it's really recent http://paste.ubuntu.com/1285353/
[16:35] <ScottK> OK.  I'll see if I can find a suitable victim to do the tests.
[16:36] <Sarvatt> shame stefan`` left since he just reported hitting it this morning, darn
[16:42] <Sarvatt> following up on his bug 1061073
[16:46] <tjaalton> well there is the regression in rendering, which doesn't affect unity anymore since it's using gles now
[16:47] <tjaalton> in i915_dri so gen3
[17:22] <bryce> mdeslaur, yeah sorry; the precise update is still on my todo list but had other pressing priorities lately.  Presently it looks like there are some issues which are going to take some work to get resolved.  I don't know the status of what's going into oneiric.
[17:23] <tjaalton> there was one nouveau patch in oneiric-proposed waiting for feedback since mid-july, so probably ok to drop it?
[17:48] <mlankhorst> well yeah :)
[20:35] <ScottK> I have a victim <- <- <- tester.
[20:43] <ScottK> Sarvatt: <StFS> ScottK: ok I'm using 9.0-git20120903 now and it sucks :(. Major artifacts and the desktop effects are very slow.
[20:43] <ScottK> So it's not a recent change.
[20:47] <ScottK> Hello StFS.
[20:47] <ScottK> Sarvatt: StFS has an affected system as well.
[20:47] <StFS> Hi
[20:48] <StFS> Sarvatt: ahh... you're the kind sould who's helping me on my bug on launchpad :)
[20:49] <StFS> I just commented. I installed mesa 9.0 git20120903 and the bug is present there... don't think there's much use in trying out the other two versions you mentioned since it clearly came before the 20120903 version.
[21:23] <mdeslaur> bryce: ok, thanks for the update. I guess we'll ignore it then and just do our update.
[21:24] <ScottK> mdeslaur: Would it make sense to copy the mesa in precise-proposed to -updates and you base off of that?  Except for your comment about the security issue, it's otherwise ready to release.
[21:25] <mdeslaur> ScottK: huh? bryce said there are issues with the package in -proposed
[21:25] <ScottK> Hmm.
[21:25] <ScottK> All the bugs are marked verified.
[21:25] <mdeslaur> ScottK: well, if that's the case, it should get pushed to -updates
[21:26] <ScottK> bryce: Should I remove mesa from precise-proposed so it doesn't get released by accident?
[21:26]  * ScottK waits for bryce.
[21:28] <bryce> ScottK, there are no known user issues.  The problem is that a couple test cases changed behavior.  According to Intel those are test suite issues not indications of user affecting problems
[21:29] <ScottK> So you'd recommend to release it?
[21:29] <bryce> ScottK, I'd have no problem releasing it.  It works fine on the hardware, aside from the piglit irregularities (which would be hard to track down)
[21:29] <ScottK> OK.  Thanks.
[21:30] <tjaalton> then we can push 8.0.5 to proposed after the security update :)
[21:31] <ScottK> bryce and mdeslaur: Done.
[21:35] <mdeslaur> bryce, ScottK: thanks
[22:13] <bryce> thanks
[22:59] <maxb> Really really weird problem on an Asus UX21A ... Pressing Fn+F5 ("brightness down") works as expected but Fn+F6 ("brightness up") when pressed multiple times seems to block until notify-osd has timed out for each level of brightness increased before the next keypress is honoured.... any thoughts? :-)
[23:02] <RAOF> I concur; that's a really weird problem :)
[23:06]  * maxb wonders if this is actually -kernel, -x or -desktop territory :-/
[23:08] <RAOF> Likely to be -desktop territory, I think?
[23:09] <bryce> maxb, there's a Hotkeys page in wiki with some tips on debugging / isolating bugs like that
[23:12]  * maxb goes to read
[23:21] <maxb> I have a sinking feeling that it could be the BIOS being dumb. The events show up delayed in xev
[23:33] <maxb> Aaanyway, looks like it's off to kernel land for me
[23:33] <RAOF> Hi ho, hi ho, it's off to kern'l we go!
[23:49] <bryce> http://www.markshuttleworth.com/archives/1195
[23:49] <bryce> Raring Ringtail
[23:49] <RAOF> Hello Possums! </edna>
[23:51] <bryce> RAOF, don't forget to snag a micro-usb (male) to usb (female) on-the-go adapter, in case you need to connect a keyboard
[23:51] <RAOF> Will do. Thanks.