[00:15] <bryceh> Sarvatt, anyway I'll assume it's not sru worthy, but poke me if it is
[02:13] <LLStarks> shocker of the night. 
[02:14] <LLStarks> xrender broken on fresh maverick
[02:14] <LLStarks> for intel
[02:18] <bryceh> oho
[02:18] <bryceh> so not a regression eh?
[02:18] <LLStarks> i can check lucid
[02:19] <LLStarks> but i was not expecting maverick to be lacking xrender.
[02:19] <bryceh> have you ruled out simple test breakage?
[02:20] <LLStarks> doubtfull. jrendermark and xrender-reliant games were also affected
[02:21] <LLStarks> btw, screen corruption test on .37 is coming up in a little bit. i'd also like to remark that the classic panel dropdown is a reliable trigger of the symptoms. anything fast moving seems to do so.
[02:21] <RAOF> Lacking xrender, or broken rendering?
[02:22] <LLStarks> err:xrender:get_xrender_format_from_color_shifts No XRender format found!
[02:23] <LLStarks> i don't know what specific files or libraries make up xrender
[02:24] <LLStarks> so i can't account for its presence or lack thereof
[02:24] <RAOF> Sounds like a server - or client - problem; xrender isn't driver dependent (although acceleration is)
[02:26] <bryceh> this is sounding like something which maybe best brought up on xorg-devel@
[02:26] <bryceh> I was thinking we could forward the bug report up to upstream bugzilla
[02:27] <bryceh> however I'll bet it needs wider eyes than that
[02:27] <bryceh> LLStarks, would you be willing to post it to xorg-devel@ for feedback?
[02:27] <LLStarks> the list? sure.
[02:27] <RAOF> Although checking whether it works on Natty first would be a good idea.
[02:28] <bryceh> RAOF, he did that already
[02:28] <bryceh> (I think he was checking maverick because I asked if it was a regression)
[02:28] <LLStarks> lucid test is coming up.
[02:28] <RAOF> Ah, fair enough.
[02:29] <LLStarks> though i'm fairly certain that i remember my games suddenly breaking during the maverick cycle
[02:29] <bryceh> RAOF, btw check it - our graph is looking quite good here at the end of the week - http://www.bryceharrington.org/X/Reports/ubuntu-x-swat/totals-natty-workqueue.svg
[02:30] <LLStarks> was maverick that bad? jeez.
[02:30] <LLStarks> *that troublesome
[02:31] <bryceh> (it'll notch down even lower once it regens, I just finished rapping down another 8-10 bugs)
[02:31] <RAOF> Sweet!
[02:32] <LLStarks> brb
[02:32] <bryceh> LLStarks, well, in maverick's defense some of the -intel freezes were out of control and apport wasn't working well enough to properly diagnose them
[02:33] <bryceh> so I think there are lots of dupes in the maverick stats which we've been better at culling out this release
[02:33] <RAOF> Also, there have been two people X'ing this cycle.  And one of them has been bryceh, master of Launchpad.
[02:34] <bryceh> however I think as a result we've been able to hone in on the bugs that *do* exist and hopefully can do good at excising them
[02:34] <bryceh> RAOF, agreed, two heads definitely better than one
[02:34] <bryceh> fwiw, the lucid graph looks about the same as the maverick one.  Manpower makes a big difference.
[02:36] <bryceh> RAOF, btw I had them shut off the retracer.
[02:37] <bryceh> it was just posting back corrupted backtraces
[02:37] <bryceh> at least this way there'll be the core file still attached so we can manually extract our own backtraces
[02:39] <bryceh> oh btw, remember the out-of-memory bug I was mentioning the other day
[02:39] <bryceh> I *think* it may be particular to USB livecd boots
[02:39] <bryceh> e.g. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/720235
[02:39] <ubot4> Launchpad bug 720235 in xorg-server (Ubuntu) "Xorg crashed with SIGSEGV in BlockHandler() (LiveCD environment, image from 20110216) (affects: 1) (dups: 1) (heat: 18)" [Medium,New]
[02:40] <RAOF> Interesting.  I wonder what's deffirent.
[02:40] <bryceh> something peculiar about the usb persistent image installation results in running out of memory
[02:40] <bryceh> yeah dunno, but suggests maybe we could reproduce it by creating usb installs in various ways
[02:41] <bryceh> however I'm EOW'd and hoping next week to focus on wayland a bit
[02:43] <RAOF> Yeah.
[02:43] <RAOF> I'll have xserver RC2 + multitouch to do for the start of next week.
[02:44] <RAOF> Oh, how did mesa/ati/xserver go?  I haven't checked if they're uploaded yet.
[02:44] <bryceh> yep, uploaded them several hours ago
[02:44] <bryceh> I booted unity and metacity with them and seemed no worse than before
[02:45] <bryceh> I still get that weird initial paint wrongness with compiz, but had that before
[02:45] <RAOF> And alt-tab works now? :)
[02:45] <bryceh> mesa might be through the buildd's
[02:45] <bryceh> oh heck, forgot to test that
[02:45] <RAOF> Well, it works *here*
[02:45] <RAOF> So I'm confident it's going to work elsewhere.
[02:46] <RAOF> Now, let's see if Civ V works on it!
[02:47] <bryceh> what was the ultimate fix?  did my patch do it?
[02:47] <bryceh> ironically as annoying as I found that, I never tested my own patch.  whoops
[02:48] <RAOF> Oh, the fix was ‘that bug doesn't apply to the gallium driver’
[02:48] <bryceh> alright on the o-o-m bug I left a note for the reporter about what I'd like to see tested; he sounded willing maybe he can do the leg work on it
[02:48] <bryceh> oh that's right, heh
[08:45] <soreau> Hello, I'm having a problem with recent updates on r300 card. First I get colored artifacts for xv video and now I cannot vnc into my box without it segfaulting X http://sprunge.us/gBIc
[09:10] <soreau> Sarvatt: I installed -dbg packages for xserver, -ati and -radeon but there seems to be no symbols still
[10:15] <ricotz> soreau, you would also need the drm dbg and mesa dbg packages
[13:46] <elderman> Hello, xsession errors prevented me from logging into a user account on my laptop.  I tracked the problem down to two functions written to my bash profile by ssh-agent.  Is this the right place to look for help?
[13:47] <elderman> I've already tried #ubuntu and the ubuntu forums
[19:15] <soreau> I'm having a problem with recent updates on r300 card. First I get colored artifacts for xv video and now I cannot vnc into my box without it segfaulting X http://sprunge.us/gBIc I installed -dbg packages for X, ddx, mesa and libdrm-radoen but it seems there are no symbols
[19:16] <soreau> gdb gives messages such as:
[19:16] <soreau> #0  0xb7630fb6 in ?? ()
[19:16] <soreau> No symbol table info available.
[19:17] <soreau> Can anyone tell me why -dbg packages do not contain debugging symbols?