[10:09] <seb128> tjaalton, mlankhorst: hey, do you know if there are any know "image corruption issue" with the new intel in saucy? it seems a bit similar to the sna one during raring but easier to trigger
[10:10] <tjaalton> seb128: I haven't noticed anything
[10:11] <tjaalton> what hw, what app?
[10:11] <seb128> i5 (ironlake?), firefox
[10:11] <seb128> quite similar to the one I pinged you about in raring
[10:11] <seb128> when you told me to try without sna (iirc)
[10:11] <seb128> I should perhaps try that again :p
[10:11] <tjaalton> yeah could be the same/worse
[10:12] <seb128> :-(
[10:12] <seb128> do you know if anyone is working on those issues upstream?
[10:12] <tjaalton> but maybe file a new bug against -intel if it's easier to hit
[10:12] <tjaalton> ickle should be
[10:13] <tjaalton> he also monitors the incoming bugs
[10:13] <seb128> bug on launchpad or fdo?
[10:13] <tjaalton> lp is fine
[10:13] <seb128> I've the issue on every second tab opening in firefox
[10:13] <seb128> on the tab summary grid
[10:13] <tjaalton> with a screenshot of the corruption in case it's not the same afterall
[10:13] <seb128> but also in chromium url bars
[10:13] <tjaalton> ah
[10:13] <seb128> and some other places
[10:14] <tjaalton> so it got worse with the -intel update?
[10:14] <mlankhorst> hm I doubt they would have released a new version if they thought it caused a regression, so just check for bugs
[10:14] <mlankhorst> or file one :)
[10:15] <tjaalton> it could be further fallout from copy-on-write support
[10:15] <tjaalton> which happened in 2.21.7
[10:15] <tjaalton> raring has .6
[10:15]  * mlankhorst appears to be hitting some regression with nouveau atm, no fun :/
[10:17] <seb128> tjaalton, yes, I had it once a day in raring, in saucy I can trigger it in 1 min
[10:18] <tjaalton> i have occasional corruption with terminator, but not in other apps
[10:18] <seb128> shrug, got another of those compiz-lock when coming back from guest
[10:18] <tjaalton> yeah still there :/
[10:19] <tjaalton> should be traced
[10:26] <seb128> tjaalton, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1189850 and https://launchpadlibrarian.net/142156716/corruption.png
[10:27] <tjaalton> seb128: thanks
[10:28] <seb128> tjaalton, it doesn't happen with uxa, I added a comment saying that
[10:31] <tjaalton> ok
[12:24] <mlankhorst> finally, isolated those nouveau lockups to a single missing flush :/
[17:11] <tjaalton> hmm, are new driver uploads pushed to both main repo and staging now?
[17:12] <tjaalton> I see the same -intel version on both
[17:13] <tjaalton> guess it's ok, just needs a new bump when copying to the archive
[17:27] <tjaalton> mlankhorst: you didn't remove test/tearing.mp4 from -intel?
[17:31] <tjaalton> heh, ppa didn't have the same version.. of course
[20:28] <bjsnider> tjaalton, is there a way i can test if i'm using sna?
[20:28] <jcristau> grep -i sna /var/log/Xorg.0.log
[20:45] <mlankhorst> tjaalton: build fails if I don't remove it, so I remove it everytime
[20:47] <tjaalton> mlankhorst: so need to remove it from the branch
[20:50] <mlankhorst> is the file from upstream? if so probably harmlless to keep
[20:50] <mlankhorst> we have to do the same for libdrm anyway
[21:06] <tjaalton> still one thing to remember every time
[21:06] <tjaalton> with libdrm it's different
[21:07] <mlankhorst> shrug, we could ask upstream about it ;)
[21:07] <tjaalton> I did
[21:07] <tjaalton> if it'll get on the tarball for the next release then it's not an issue