[00:00] <RAOF> The wishlist bugs session sounds like a good one to me.
[00:06] <bryceh_> RAOF, ok I'll craft a blueprint
[00:06] <bryceh_> RAOF, meanwhile it seems one of monday's updates introduced a regression - see bug 757968
[00:06] <ubot4> Launchpad bug 757968 in xserver-xorg-video-intel (Ubuntu) "[i965gm] GPU lockup (IPEHR: 0x14000000) - Black screen (affects: 2) (dups: 1) (heat: 14)" [High,Confirmed] https://launchpad.net/bugs/757968
[00:08] <bryceh_> RAOF, any ideas offhand?  If the user can repro it, I'm going to have them individually downgrade mesa, xserver, -intel, and compiz to see which causes it.
[00:08] <RAOF> bryceh_: looking.
[00:08] <bryceh_> if I were to bet, I'd guess mesa.
[00:09] <RAOF> Me too.
[00:10] <RAOF> If it's reproducible, and downgrading mesa fixes it, it shouldn't be too hard to identify the bad commit.
[00:13]  * bryceh_ nods
[00:13] <bryceh_> alright, sounds like a plan
[00:16] <bryceh_> RAOF, btw I have a suspicion the libdrm patch ickle gave us is bad
[00:16] <RAOF> The even-more-relaxed-tiling fixes one?
[00:16] <bryceh_> I've got 2-3 similar-ish bugs that I've got traced to regressing around the time that patch went in
[00:17] <RAOF> Hm.
[00:17] <bryceh_> so far one test of downgrading it indicates that without that patch it freezes less often (maybe there's another freeze bug)
[00:18] <bryceh_> the bugs are freezes and/or black screen issues
[00:18] <bryceh_> so, if I can gather some more solid evidence I might revert that patch...100_intel_remember_named_bo.patch
[00:20] <bryceh_> RAOF, I do note that debian took a couple other patches along with that one for 2.4.23-3, so perhaps one of them corrects issues that this patch brought?
[00:20] <RAOF> Fun fact: ‘break WriteToClient if who=0x14f92d0’ is *very importantly* not the same as ‘break WriteToClient if who==0x14f92d0’ :)
[00:21] <Sarvatt> that or there were more parts of 2.4.24 needed too
[00:21] <RAOF> bryceh_: Possibly?
[00:21] <RAOF> The other parts of 2.4.24 *claimed* to be about older kernels, and certainly looked that way.
[00:21] <bryceh_> right
[00:22] <bryceh_> if I can confirm that downgrading solves these issues, I can also see about having them test against the newer version if it's in a ppa somewhere
[00:23] <Sarvatt> these time zone differences between us all suck :)
[00:23] <bryceh_> anyway, thinking we should hold off on 2.4.24 until these regressions are better understood
[00:23] <bryceh_> Sarvatt, howso?
[00:24] <RAOF> I can upload 2.4.24 into X staging pretty easily.
[00:25] <bryceh_> ok, that sounds like a good step
[00:25] <bryceh_> I'll have folks test against that
[00:32]  * RAOF turns on the coffee machine and sets to uploading.
[00:51] <RAOF> Uploaded to ubuntu-x-swat.
[01:14] <RAOF> AAaand built.
[01:14] <bryceh_> thanks
[07:22] <tjaalton> bryceh_: whoopsie daisy.. done
[09:07] <njpatel> RAOF, I loved seeing that email in the morning....thank you for your work helping to track this down :)
[09:08] <RAOF> njpatel: It's a nice thing to end the week on :)
[09:08] <njpatel> Indeed :
[09:08] <njpatel> :)
[09:34] <ara> good morning tseliot
[09:34] <tseliot> good morning to you ara :)
[10:45] <seb128> bryceh_, some of the duplicates of the "intel_tex_image.c:726: intelSetTexBuffer2: Assertion `!texImage->Data' failed" have apport infos if that's useful
[11:46] <bradm> hi, is there anything I can do to help with bug 727620?  I have to reboot my laptop 5 or 6 times, and then log into and kill X about the same before I get a usable session
[11:46] <ubot4> Launchpad bug 727620 in xserver-xorg-video-ati (Ubuntu) (and 2 other projects) "[Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4) (affects: 9) (dups: 1) (heat: 58)" [High,Incomplete] https://launchpad.net/bugs/727620
[12:21] <tjaalton> bradm: why don't you use the workaround mentioned in comment #26
[12:24] <bradm> tjaalton: I did try that and had some issues, should give it another go I guess.  it'd be good to have the bug fixed though
[12:26] <tjaalton> bradm: strongly in the upstream territory though, it needs kernel changes that won't get in 2.6.38
[12:26] <tjaalton> from what I can tell anyway
[12:26] <bradm> tjaalton: right, I suspected that might be the case but its not really 100% clear in the bug thats whats happening
[12:27] <tjaalton> bradm: have you looked at the upstream bug?
[12:28] <bradm> tjaalton: I did
[12:28] <tjaalton> "The switcheroo code
[12:28] <tjaalton> needs more work to switch properly on some systems it seems."
[12:29] <bradm> yes, there's a lot of it seems, and supposition, was just wondering if I could do anything to help clear it up
[12:29] <bradm> its not clear to me whats happening now with the bug
[12:31] <tjaalton> i can confirm it if you like
[12:31] <tjaalton> the bug report, not the bug happening
[12:32] <bradm> well, it does say status incomplete, made me think something was missing
[12:32] <tjaalton> there
[12:33] <bradm> cool, thanks
[12:34] <bradm> its definately still happening for me at least
[12:34] <tjaalton> i don't doubt that
[12:35] <bradm> oddly I couldn't see anything in my bios to tell it to just use the radeon, but it is downrev a bit
[12:35] <bradm> but it needs windows to do a bios update :-/
[12:37] <tjaalton> it's updated from windows?
[12:37] <bradm> all HP provide is a windows .exe
[12:37] <bradm> its possible there's a way of flashing from linux but its not obvious from the time I've spent looking 
[12:38] <bradm> which, admittedly, hasn't been an enormous amount
[12:42] <tjaalton> it's usually just a self-extracting zipfile
[12:42] <tjaalton> use unzip to extract it
[12:43] <tjaalton> there are docs for creating a bootable cd that you can use for flashing your bios
[12:44] <bradm> nope, its not a zip file
[12:45] <bradm> ah, its a cab file
[12:45] <tjaalton> have a link to it?
[12:46] <bradm> ftp://ftp.hp.com/pub/softpaq/sp50501-51000/sp50942.exe
[12:50] <bradm> I've found some references that say the bios is encrypted by one of the dlls provided
[12:55] <tjaalton> right, that tool really needs windows..
[12:55] <tjaalton> fail
[12:59] <bradm> very much so
[12:59] <bradm> my next laptop won't be a HP :)
[13:57] <BlackZ> Sarvatt: I filed a bug for the issue I described you the other day: bug #761718
[13:57] <ubot4> Launchpad bug 761718 in nvidia-graphics-drivers (Ubuntu) "Can't start Ubuntu default session properly (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/761718
[14:07] <tseliot> BlackZ: what happens if you downgrade to the previous version of nvidia-current  and reboot?
[14:08] <BlackZ> tseliot: this is what I was just trying ;)
[14:08] <tseliot> everything seems to be ok, BTW
[14:08] <BlackZ> yeah, looks quite weird
[14:44] <BlackZ> tseliot: downgrading to the previous version doesn't help at all
[14:44] <BlackZ> (and I was having the problem what that version as well)
[14:44] <tseliot> BlackZ: I suspected that. It means that something else busted your system. Maybe unity?
[14:45] <BlackZ> tseliot: I don't think so. Even the classic Ubuntu session doesn't start properly
[14:45] <BlackZ> tseliot: I can only start the one without any effect
[14:45] <tseliot> BlackZ: it's probably compiz then
[14:46] <BlackZ> tseliot: yeah, I think so
[14:46] <tseliot> BlackZ: see if you can find something interesting in your ~/.xsession-errors after you reproduce the problem
[14:47] <BlackZ> tseliot: unfortunately no, I can't
[14:48] <tseliot> BlackZ: can you reproduce the problem if you start the classic session without effects and then type: compiz --replace
[14:48] <tseliot> ?
[14:57] <BlackZ_> tseliot: bingo! the problem is compiz..
[14:57] <BlackZ_> tseliot: it seems to crash at "Starting unity-window-decorator"
[14:58] <tseliot> BlackZ_: ok, please update the bug report and assign the bug to compiz
[14:58] <BlackZ_> tseliot: will do! thanks :)
[15:00] <BlackZ_> tseliot: btw I still can't figure out why it works with the nouveau drivers..
[15:18] <bjsnider> why don't the other nvidia users have th is bug?
[15:18] <bjsnider> me, for example
[15:51] <BlackZ_> bjsnider: no clue, this is really really weird
[19:45] <cnd> bryceh_, got a bug fix for evdev pushed to git for bug 573006
[19:45] <ubot4> Launchpad bug 573006 in xserver-xorg-input-evdev (Ubuntu) (and 1 other project) "Touch screen driver clicks at wrong location (affects: 8) (heat: 52)" [Medium,New] https://launchpad.net/bugs/573006
[19:45] <cnd> please upload when it's convenient
[19:49] <bryceh_> cnd, ok will do
[20:44] <cnd> bryceh_, got a fix for synaptics bug 754470 pushed to git too :)
[20:44] <ubot4> Launchpad bug 754470 in xserver-xorg-input-synaptics (Ubuntu Natty) (and 2 other projects) "syndaemon consumes 100% CPU (affects: 65) (dups: 4) (heat: 342)" [High,In progress] https://launchpad.net/bugs/754470
[21:44] <tjaalton> cnd, bryceh_: pushed the reverted patch for bug 757972 to git
[21:44] <ubot4> Launchpad bug 757972 in xorg-server (Ubuntu) (and 2 other projects) "Easystroke doesn't recognize button release (affects: 5) (heat: 30)" [Medium,In progress] https://launchpad.net/bugs/757972
[21:45] <cnd> tjaalton, thanks!
[21:45] <tjaalton> cnd: sorry for just throwing the ball on your court yesterday ;)
[21:46] <cnd> tjaalton, np :)
[21:46] <cnd> it's a bit of a lull right now
[21:46] <cnd> and it very well could have been caused by some of my patches
[21:47] <tjaalton> heh, well your patches were, for the most part, already on our tree
[21:47] <tjaalton> in
[21:48] <tjaalton> aanyway, seems that there are less bugs flowing in that I feared
[21:48] <tjaalton> beta2 and all
[21:50] <tjaalton> some freezes yeah, but could just as well be compiz ones
[21:53] <tjaalton> and i really hope/believe that bug 507602 is finally fixed by libx11 1.4.2
[21:53] <ubot4> tjaalton: Bug 507602 on http://launchpad.net/bugs/507602 is private
[21:53] <tjaalton> duh
[21:53] <tjaalton> bug 507062
[21:53] <ubot4> Launchpad bug 507062 in libx11 (Ubuntu Natty) (and 3 other projects) "synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed. (affects: 407) (dups: 267) (heat: 2474)" [Medium,Incomplete] https://launchpad.net/bugs/507062
[21:54] <tjaalton> 267 dupes..
[21:54] <tjaalton> there's more, I'm sure
[21:54] <bryceh_> wow
[21:55] <tjaalton> i ran the test code on the upstream bug for an hour or so, and couldn't reproduce it
[21:55] <tjaalton> though I should probably try it on beta1 too, to see if the code actually works
[21:58] <mvo> tjaalton: I think I saw a similar one for software-center recently, same pattern
[21:59] <tjaalton> mvo: yeah, many of those are from s-c
[21:59] <mvo> bug #761972
[21:59] <ubot4> mvo: Bug 761972 on http://launchpad.net/bugs/761972 is private
[21:59] <mvo> why my stuff? synaptic, software-center? *grumpf* ;)
[22:00] <tjaalton> heh
[22:00] <tjaalton> ah well
[22:00] <tjaalton> so it's a fresh one, probably didn't fix it then
[22:00] <tjaalton> duh
[22:01] <bryceh_> mvo, you're not alone.  Many times I've gone to report an emacs, xterm, firefox, etc. bug only to end up finding out it's actually a friggin X bug.
[22:01] <mvo> at least I'm not alone!
[22:02] <tjaalton> there are also some interesting commits on the libxcb tree, but it's a risky business pulling those. there really should be a reliable way to trigger this, but I'm afraid that's asking for too much..
[22:13] <bryceh_> yeah, we've been burned with xcb cherrypicks in the past.  quite a fragile library
[22:13] <bryceh_> reboot time. bbiab
[22:13] <tjaalton> best to try it via an sru
[22:13] <tjaalton> or oneiric..
[22:13] <tjaalton> most likely
[22:19] <bryceh> cnd, [ubuntu/natty] xserver-xorg-input-synaptics 1.3.99+git20110116.0e27ce3a-0ubuntu12 (Waiting for appro
[22:19] <bryceh> cnd, [ubuntu/natty] xserver-xorg-input-evdev 1:2.6.0-1ubuntu12 (Waiting for approval)
[22:19] <cnd> bryceh, ta!
[22:28] <Sarvatt> darn, i started packaging up a new libxcb but gave up halfway through the 100+ new symbols. guess i should finish it :P