[03:44] <tjaalton> bryceh: yeah, and I kinda wanted to have a separate bug like the one mdeslaur filed, just for that. but it got duped again :)
[03:44] <tjaalton> sna would be one thing to try, even though it has backlight issues atm
[03:48] <tjaalton> looks like sna fixed thumpers bug
[03:48] <tjaalton> +'
[04:06] <bjsnider> tjaalton, i've just gotten into the finnish symphonic metal/black metal scene. i'm sure it's commonplace in finland, but it came as a complete surprise to me
[04:06] <bjsnider> i'm convinced that the best and most interesting music in the world is coming out of finland
[04:10] <tjaalton> bjsnider: hehe
[04:11] <tjaalton> yeah quite a few groups on that genre
[04:22] <bjsnider> and they're genuises, all of them
[06:12] <tjaalton> czajkowski: ping me when you're around, got something you could try
[06:39] <mlankhorst> morning
[06:40] <tjaalton> yawn
[06:40] <mlankhorst> precisely
[06:41] <mlankhorst> too early for fencing :(
[06:41] <tjaalton> bryceh: btw, I find the release targeted buglists (linked from totals-foo-workqueue) hugely useful
[06:41] <tjaalton> otherwise the bugs would get lost in the noise
[06:45] <mlankhorst> yeah they are
[06:46] <tjaalton> especially now as it lists incomplete bugs too
[06:46] <tjaalton> i think before they were excluded
[07:02] <bryceh> tjaalton, oh good to hear, yeah I use them a lot too
[07:02] <bryceh> there's two kinds of incomplete bugs:  "With response" and "Without response".  The list excludes the latter only.
[07:02] <tjaalton> ahh
[07:03] <bryceh> that way if you ask a question and someone answers it, it'll pop back up on your list
[07:03] <bryceh> but be aware if like I ask a Q and set to Incomplete, then you follow up with another question and leave it Incomplete, your comment will result in it turning into "With response"
[07:04] <bryceh> so, when adding questions to an incomplete bug, just set it to New, then ask your Q and set back to incomplete, and that'll keep it off this list.
[07:04] <tjaalton> heh, well that doesn't matter much, not much noise there anyway
[07:04] <tjaalton> yet
[07:05] <bryceh> tjaalton, did you see someone went through and tested a bunch of obscure video drivers and gave us bugs on each?
[07:05] <bryceh> well, 3-4 bugs.  still, cute.
[07:05] <tjaalton> bryceh: on quantal?
[07:05] <bryceh> yeah
[07:06] <tjaalton> oh, didn't notice it was the same guy
[07:08] <tjaalton> ../../src/trident_dga.c:40:13: warning: 'TRIDENT_Sync' used but never defined [enabled by default]
[07:36] <ricotz> bryceh, hi :)
[07:37] <bryceh> heya ricotz 
[07:37] <ricotz> bryceh, i wondering if there is some policy to join the ubuntu-x-swat group?
[07:37] <ricotz> i am *
[07:37] <bryceh> ricotz, there's definitely a policy I enforce
[07:37] <bryceh> ricotz, but you definitely qualify.  :-)
[07:38] <ricotz> bryceh, i thought about to join, but wasnt sure if i qualify ;)
[07:38] <tjaalton> ha, ok both trident and mga failures are due to sloppy xaa removal work :)
[07:38] <ricotz> bryceh, but while i saw the latest joins i got confused a bit
[07:38] <bryceh> ricotz, you do, go ahead and apply and I'll approve you.  Thanks for asking first though, I appreciate it!
[07:38] <bryceh> tjaalton, heh
[07:39] <tjaalton> time to send patches then
[07:40] <ricotz> bryceh, done
[07:40] <bryceh> ricotz, yeah I admit the last couple approved members I felt marginal about their qualifications but they seemed interested.  I suspect they'll expire out.
[07:41] <ricotz> bryceh, i see, dont worry then
[07:43] <bryceh> I usually tell people what membership in ubuntu-x-swat implies (i.e. packaging work), and ask what they plan to use it for.  That seems sufficient to ward off most people who are just collecting badges or whatever.  The last couple people expressed interest in doing bug triage work.  We definitely need more triagers so I gave them the benefit of the doubt, and hope they do get involved.
[07:44] <ricotz> bryceh, that is perfectly fine
[07:46] <bryceh> ricotz, welcome to swat :-)
[07:46] <ricotz> bryceh, thanks, yeah a new badge ;P
[07:46] <tjaalton> now filter your email :)
[07:47] <ricotz> tjaalton, i am already spammed with all kind of things ;)
[08:23] <tjaalton> oh heh, we've uploaded -mga 1.6.1 as 1.6.0
[08:23] <tjaalton> by we I mean me
[08:23] <mlankhorst> the royal we
[08:23]  * mlankhorst testing vblank on patch
[08:36] <tjaalton> chrisccoulson: hey, you were able to hang compiz like everyone else?
[08:36] <tjaalton> on suspend/screensaver
[08:37] <chrisccoulson> tjaalton, yeah, although i've set "Turn screen off when inactive" to "Never" in the control centre now, to avoid it :)
[08:38] <tjaalton> chrisccoulson: understood :) was just wondering if you could try the newer acceleration method to verify it doesn't happen there
[08:38] <tjaalton> though it has issues of it's own, but not this severe
[08:38] <tjaalton> at least here
[08:38] <chrisccoulson> tjaalton, yeah, can do. although it'll need to wait a few minutes for some other stuff to finish first
[08:39] <tjaalton> chrisccoulson: sure thing, you can check out the typo'ed xorg.conf from bug 1043562
[08:39] <mlankhorst> seems that my vblank patch works, even though that card has no output :x
[08:40] <tjaalton> chrisccoulson: so comments #4 & 5
[08:40] <chrisccoulson> tjaalton, yeah, will do
[08:41] <tjaalton> it'll hit bug 1055987, but a simple vt change will remedy that
[08:49] <tjaalton> hmm, wonder if we should provide a build of -intel with --enable-debug
[08:50] <RAOF> Sounds like a job for xserver-xorg-video-intel-dbg!
[08:51] <tjaalton> oh you mean build two versions and ship the other one with -dbg?
[08:51] <tjaalton> --enable-debug adds debugging output to the logfile
[08:53] <tjaalton> I was thinking more like putting the other one in a ppa :)
[10:01] <tjaalton> chrisccoulson: had time to test yet? you can speed it up by changing the screen off timer to one minute, and then go through a couple of cycles
[10:02] <tjaalton> enough to make sure it would've hung before
[10:02] <tjaalton> and vt changes in between to wake the backlight :)
[10:04] <RAOF> tjaalton: I mean build two versions and ship the other one with -dbg, yes.
[10:07] <RAOF> You know what they say - built twice, ship once.
[10:10] <tjaalton> yeah, why not
[10:42] <chrisccoulson> tjaalton, i've got a job running over SSH at the moment. i need to wait for that to finish before i risk anything that might result in me needing to reboot :)
[10:44] <mlankhorst> guess I'll see if I can fix the quantal stack
[10:47] <tjaalton> chrisccoulson: ok gotcha :)
[10:47] <seb128> chrisccoulson, tjaalton: is that the blank screen after dpms issue?
[10:47] <chrisccoulson> seb128, yeah
[10:47] <seb128> where is the fix to try?
[10:49] <tjaalton> seb128: trying if 'Option "Accelmethod" "sna"' works around it
[10:50] <tjaalton> it would at least narrow it down to the uxa code in the -intel driver..
[10:50] <tjaalton> heard positive results from it so far
[10:50] <seb128> tjaalton, you don't have a full xorg.conf I could copy by any chance?
[10:51] <tjaalton> seb128: hang on
[10:51] <tjaalton> seb128: can you reproduce it at will?
[10:51] <seb128> I tried to not run often into it, but I got it the only time I let my screen go to idle the other day
[10:51] <seb128> and I got it today when I undocked my laptop
[10:52] <tjaalton> ok, "good"
[10:52] <seb128> (though the undock could be another issue)
[10:53] <tjaalton> http://pastebin.com/nb6zhmcE
[10:58] <mlankhorst> tjaalton: can you upload xxv-nouveau to quantal-proposed? (I guess archive is still frozen)
[11:00] <tjaalton> mlankhorst: -proposed is reserved for transitions, we can upload to quantal and it'll reopen after the beta
[11:01] <mlankhorst> hm ok
[11:09] <mlankhorst> Yeah seems the dpkg-control script creates slightly broken packages
[11:10] <tjaalton> example?
[11:11] <mlankhorst> every line with Replaces/Breaks/Provides/Conflicts that has a package name on the same line ends up with those packages being eaten entirely
[11:12] <tjaalton> oh that
[11:14] <mlankhorst> now confirmed it with random packages, but need to have this solved :-)
[11:21]  * mlankhorst tries horrible hack
[11:51] <tjaalton> seb128: did you get the pastebin link?
[11:55] <seb128> tjaalton, yes, thanks, did restart yet though, I will try that in a bit
[11:55] <tjaalton> seb128: ok, good
[12:02] <tjaalton> ha, reproduced the hang on one of my machines
[12:02] <tjaalton> finally
[12:02] <tjaalton> but it took several cycles
[12:22] <tjaalton> chrisccoulson, seb128: I'll take it back, testing sna isn't worth it. I'll build a test kernel with the crack-of-the-day..
[12:22] <seb128> tjaalton, ok
[12:26]  * mlankhorst gives up on gpg key for now, creates new one
[12:38] <tjaalton> ok, building a drm-dkms package for quantal..
[13:07] <mlankhorst> uploading ppa5 with the packages fixed :)
[13:55] <mlankhorst> hopefully the issues I came across with the packages being borked day before the demo are gone now
[13:56] <tjaalton> cool
[13:56] <tjaalton> building ubuntu-r git + drm-intel-next-queued..
[13:56] <tjaalton> hoping to retain overlayfs so sbuild works
[13:57] <mlankhorst> Hah, you're building on dinq, I'm working on the code that eventually ends up there. :P
[13:58] <tjaalton> we'll see if it builds
[13:58] <mlankhorst> With intel qa, that's probably the only thing that works for sure
[13:58] <tjaalton> heh
[14:00] <tjaalton> gave up on the drm-dkms idea, not going to work
[14:00] <tjaalton> crazy changes
[14:00] <mlankhorst> hard to keep track of all, even..
[14:06] <tjaalton> yeah, and irreversible changes ouside of drm
[14:06] <tjaalton> well, not worth the effort anyway
[14:20] <mlankhorst> wow, new nouveau kernel source.. I just don't get it..
[14:23] <tjaalton> kernel buil
[14:23] <tjaalton> t
[14:24] <tjaalton> let's see if it works at all
[14:25] <tjaalton> nope :P
[14:26] <mlankhorst> so many spinlocks just called 'lock' with no clue what it protects
[14:26] <mlankhorst> which is fun if foo->lock exists and you also have a foo->base.lock
[14:52] <tjaalton> recorded the kernel oops with my phone, need to slow it down so I can see where it started :)
[14:54] <tjaalton> need more hurts
[14:54] <tjaalton> the machine is too fast
[14:58] <tjaalton> moo, why doesn't shift-pgup work
[15:04] <mlankhorst> no wonder things were failing, I made it act like work was still being done after it was already completed
[15:17] <mlankhorst> yay, working now \o/
[17:05] <om26er> hi, latest nvidia driver breaks autohide in unity we are getting reports
[17:05] <om26er> 304.51
[17:06] <om26er> bug 1057000
[18:21] <bjsnider> does the .51 driver still support the 7300gt?
[18:24] <bjsnider> i'd like to know if it happens on present-day hardware
[20:38] <mlankhorst> probably should
[20:39] <mlankhorst> hm it's a nv46
[20:39] <mlankhorst> not going to be supported in the next one at least
[20:51] <bryceh> RAOF, hey, for the nvidia experimental packages in NEW right now, since you're an archive admin are you empowered to wave them through?  Or can you handle only the SRU approval bit?
[20:53] <bryceh> I'd like to get the 304 packages all the way to the end of the process prior to a "real" beta driver appearing so we know all the t's are crossed and i's dotted.  But in general I wonder if we need to streamline some of the review policies...
[23:04] <RAOF> bryceh: I'm not a real archive admin ☹.
[23:07] <bryceh> RAOF, I've gotten infinity on -devel who is taking care of it.
[23:15] <bjsnider> RAOF is pretending to be an archive admin. actually he's a british spy under cover, and now he's admitted it
[23:52] <bryceh> RAOF, the experimental drivers are now in precise-proposed.  Quick question for you with your SRU approver hat on: Since we are expediting this package as per TB, how long will the drivers need to sit in -proposed?
[23:55] <RAOF> bryceh: I'm hunting the actual TB mail, but generally the answer would be ‘until it's been tested to work’ - we don't necessarily have to have the 7-day cooling off period.
[23:57] <bryceh> ok