[00:00] <RAOF> bryceh: I've just got a backtrace from the xorg apport hook: http://paste.ubuntu.com/647730/
[00:00] <RAOF> Are you aware of this?
[00:07] <bryceh> no hadn't seen it
[00:07] <bryceh> thanks
[01:15] <bryceh> fixed
[01:16] <bryceh> RAOF, push git on xorg
[01:17] <RAOF> Bah.  Done.
[01:17] <bryceh> thanks
[01:29] <bryceh> ok, I'm going to work on xdiagnose a bit more but am done fussing with X bugs for today.
[01:29] <bryceh> RAOF, the queue's knocked down a bunch, but here's what's left:  http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/workqueue-oneiric.html
[01:30] <RAOF> That's looking pretty healthy for the moment!
[01:30] <bryceh> keep in mind that list doesn't include bugs we've set as incomplete and are waiting on people to respond on
[01:31] <bryceh> that's just ones that you and I need to do something
[01:31] <bryceh> but yeah, even the "all bugs reported" status look ok:  http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/totals-oneiric.svg
[01:32] <bryceh> of course I worry that the bug you found in the apport hook might have been preventing people from filing bugs....
[01:35] <bryceh> http://www.bryceharrington.org/Arsenal/Reports/ubuntu-x-swat/totals-oneiric-workqueue.svg
[01:38] <RAOF> Look at that!  We fixed all the bugs just in time last cycle :)
[01:39] <bryceh> something like that ;-)
[01:39] <bryceh> we're definitely doing better than last cycle
[01:40] <bryceh> last time we started at 0 and did pretty well
[01:40] <bryceh> this time we started with 20 bugs, that I pulled forward from natty, and we're back down to 20 today
[01:47] <RAOF> Man, it'll be good to have the vblank-when-disabling-outputs kernel in natty-updates; I'd guess at least one commenter on slangasek's -intel GPU hang bug is hitting that.
[01:51] <bryceh> yeah
[01:52] <bryceh> RAOF, you might also look at whether some of the mesa gpu fixes would be worth putting into natty's mesa as sru's
[01:54] <RAOF> Yeah.  If they apply ;)
[07:08] <apw> RAOF, i see that the testing results on bug #753994 are good, but i also see keith asking for updates (to comments)
[07:08] <ubot4> Launchpad bug 753994 in linux (Ubuntu Oneiric) (and 2 other projects) "[arrandale] Display is slanted when using 1360x768 resolution (affects: 1) (heat: 8)" [Medium,Confirmed] https://launchpad.net/bugs/753994
[07:09] <RAOF> apw: Yeah.  I presume that's why I couldn't find it in any upstream kernel tree.
[07:10] <apw> RAOF, i see no response from the submitter updating it unless they also updated the title
[07:11] <RAOF> apw: I haven't seen any response, either; I don't think that's an artefact of title updating.
[07:12] <RAOF> I guess I'll send a Tested-By: reply and see if ajax wants to address the comments.
[07:22] <diverse_izzue> bryceh, ping
[07:22] <apw> RAOF, good idea
[07:22] <RAOF> Which is exactly what I've done :)
[07:22] <RAOF> diverse_izzue: It's probably a bit late for bryceh.  Can I help you?
[07:23] <apw> RAOF, heh ... as it sounds like its just comment updates that doesn't preclude us from starting the SRU process
[07:23] <apw> cirtainly if there is no response 'soon'
[07:23] <RAOF> apw: You'd need to pull it into the current kernel first! :P
[07:24] <apw> RAOF, heh yeah, well frankly thats the norm as the devel kernel is always off from mainline too these days
[07:24] <diverse_izzue> ROAF, I don't know his time zone. I reported this bug (811640), and he responded by asking me to install a PPA (ppa:bryce/melon). However the xorg-server in that PPA is not new enough to supersede what's in oneiric, so I'm not sure that PPA will do what he intended.
[07:26] <diverse_izzue> RAOF, the above is for you, but is misspelled your name :-)
[07:28] <RAOF> Yeah.  I was just looking at the bug.  So, you *could* install those packages manually, and they should work (until you next update, at which point they'll be upgraded to the newer oneiric versions).  Or you could wait for tomorrow when bryceh will hopefully have oneiric packages in that PPA :)
[07:30] <diverse_izzue> RAOF, they are oneiric packages, but i think there was just an xorg update pushed to oneiric, which is why the ppa ones are already not new enough.
[07:30] <RAOF> Ah.  That's right, I stopped upgrades from dying.
[07:31] <diverse_izzue> RAOF, don't understand
[07:31] <RAOF> I updated the xorg package yesterday to fix an upgrade bug.
[07:32] <diverse_izzue> is there a way to give a ppa a higher priority than the main repos?
[07:33] <RAOF> There is, but you probably don't want that.  Just do an ‘aptitude install xserver-xorg-core=$THE_VERSION_IN_THAT_PPA’, and then don't update before rebooting ;)
[07:33] <diverse_izzue> oh, ok, and will that automatically pull the right versions of other stuff built from that source package?
[07:37] <RAOF> To satisfy dependencies, yeah.
[07:40] <diverse_izzue> RAOF, thanks for the help, will now try
[08:29] <jibel> bryceh, latest xdiagnose introduced bug 813367
[08:29] <ubot4> Launchpad bug 813367 in xdiagnose (Ubuntu) "xorg apport hook fails with TypeError: list indices must be integers, not list (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/813367
[12:02] <albert23> Ah, sna also wants "shm: Replace open-coded version of GetScratchPixmapHeader". Now I understand the sna comments in the desktop meeting :-)
[15:00] <bjsnider> ricotz, you're now starting to package gnome-shell extensions?
[15:20] <ricotz> bjsnider, the package is available for 2 months ;) -- actually cdbs started it
[15:45] <bjsnider> last i read the gnome recommendation was not to package any of them
[15:50] <ricotz> bjsnider, this doesnt sound useful, where do you read this?
[15:54] <ricotz> some of them must be installed in /usr because of gsettings schemas which isnt recommended for end-users
[16:11] <bryceh> jibel, thanks; investigating
[16:31] <kees> say, I've noticed that my laptop sees i915 waking up 60 times a second... is there some way to diagnose this so I can get some battery life back/
[16:33] <kees> (this is on natty btw)
[16:43] <bryceh> kees, look in your logs for error messages, turn on more debugging messages, look at modinfo i915 for any tunables, re-test on oneiric kernel, and if all else fails contact jbarnes
[16:44] <bryceh> kernel team might have more structured diagnostics; generally we punt power and suspend type issues over to them.
[16:52] <tjaalton> kees: and disable the blinking cursor if it's on, also check if the panel clock displays seconds..
[16:56] <kees> tjaalton: oooh, blinking cursor!
[16:56] <kees> let me try that first...
[16:57] <kees> tjaalton: hm, no change there
[17:01] <tjaalton> kees: duh, should've helped
[17:02] <kees> tjaalton: powertop still shows 60 wakeups a second :(
[17:04] <kees> tjaalton: any idea how to debug this?
[17:15] <jcristau> kees: running compiz?
[17:20] <kees> jcristau: yeah. I don't remember it doing that before, though
[17:21] <jcristau> maybe pageflip didn't work before
[17:21] <kees> hmpf.
[17:21] <tjaalton> kees: (sorry, got disconnected) it's probably some x client causing it, like compiz as jcristau suggested
[17:21]  * kees waves goodbye to battery life
[17:26] <albert23> or use unity-2d, that's low power
[17:26] <kees> yeah
[17:35] <bryceh> kees, newer powertop has some trace points for tracking things like this, and might give the pid of what client is being naughty
[17:36] <bryceh> kees, 60 wakes/sec sounds like something using vblank events
[17:38] <kees> bryceh: yeah, so it probably is compiz. I'm going relogin in here in a second...
[17:40] <bryceh> kees, if you definitively narrow it to compiz; might check by disabling plugins.
[17:40] <bryceh> er, might *also* check
[17:43] <jcristau> letting the compositing manager synchronise updates with vblank is what this interrupt is all about, so i'm not surprised it shows up...
[17:49] <bryceh> drm_vblank_event_delivered in /sys/kernel/debug/tracing/events/drm sounds like it might give the pid of what's getting the events
[17:50] <jcristau> i suppose the interrupt could be disabled when there's nothing to draw though...
[17:50] <bryceh> yeah
[17:51] <jcristau> dunno if that's supposed to be implemented, i haven't been paying too much attention :)
[17:53] <bryceh> or implemented but off due to bugs
[17:57] <albert23> switching off sync to vblank in compiz, opengl plugin seems to work
[17:57] <bryceh> albert23, gconf setting?
[17:57] <albert23> ccsm
[17:57] <bryceh> kees, ^
[17:59] <bryceh> kees, also I don't know if you already looked but modinfo i915 shows tunables for fiddling rc6 (render c6 deep sleep) and fbc (framebuffer compression).
[18:00] <bryceh> those probably won't affect the wakeup problem though.  rc6 sleep may give you some suspend power improvements if you have it turned off.
[18:01] <bryceh> kees is quiet now; perhaps he ran out of power?  ;-)
[18:42] <ricotz> bjsnider, i was hoping that tseliot uploaded the new nvidia blob to oneiric, but it didnt :\
[18:42] <ricotz> he*
[19:18] <bjsnider> ricotz, which, the 275.19 or the 280?
[19:19] <ricotz> bjsnider, 275.19
[19:19] <bjsnider> i can throw it into x-updates based on his most recent build scripts
[19:19] <bjsnider> the source package is already there, which is the big deal with the blob. it's very large
[19:21] <bryceh> tseliot's probably tied up with oem work or something.  I've not talked to him in some time
[19:21] <bjsnider> i think oneiric users should be ont he 280 at this point because of the recent kernels/x-server support though right?
[19:21] <bryceh> there's several oneiric packaging bugs with -nvidia if anyone wants to take a look.  look like simple path checking issues and such
[19:21] <bjsnider> bryceh, he said he'd put it in there not long ago. he might have forgotten
[19:21] <bryceh> bjsnider, sounds about right
[19:30] <ricotz> as long there is no xserver 1.11 in oneiric using the stable 275.x should be the one
[19:31] <ricotz> 280.x doesnt feel that stable for me currently 
[19:33] <bjsnider> what's the xserver version in oneiric right now?
[19:33] <ricotz> bjsnider, putting it it x-updates would be nice for now
[19:33] <bryceh> oneiric has 1.10 and 275.09.07
[19:33] <ricotz> i think 1.10.2
[19:34] <bjsnider> when is 1.11 going in?
[19:34] <bryceh> 1.10.2.902
[19:34] <bryceh> 1.11 isn't going in for oneiric
[19:34] <ricotz> is this final yet?`
[19:34] <bryceh> yep
[19:34] <ricotz> ok
[19:34] <bjsnider> that's kind of conservative
[19:34] <bryceh> well, 1.10.3 will be final
[19:35] <bryceh> unless there's a 1.10.4 that looks important
[19:35] <ricotz> or 1.10.4 ;)
[19:35] <ricotz> :P
[19:35] <bryceh> bjsnider, precisely
[19:36] <bryceh> I don't know if 280 is going to make it into oneiric, but like I said sounds right for x-updates probably
[19:36] <bryceh> but up to you guys; if you think it's unstable then perhaps wait.
[19:36] <ricotz> no, 275 should go in x-updates
[19:36] <bjsnider> it's marked beta
[19:37] <bjsnider> does the 275 build with the oneiric kernel?
[19:37] <ricotz> bjsnider, yes, it is already in the repos
[19:38] <ricotz> they patched it for 3.0 awhile ago
[19:38] <bryceh> like I said there's been some packaging bugs reported, but they seem to be corner cases
[19:38] <ricotz> yeah, there are probably multiarch problems
[20:44] <bjsnider> ricotz, the package is now available for amd64
[21:22] <ricotz> bjsnider, thanks :)