[04:47] <pwnguin> damn bryce
[04:48] <pwnguin> i guess tagmail is my punishment for ignoring wacom
[05:54] <tjaalton> pwnguin: nonsense, those bugs are assigned to me ;)
[05:57] <tjaalton> two exams left this week, hopefully I'll be able to update wacom to support intuos4 after that..
[09:59] <Ng> bryce: downgrading mesa did indeed get me working compiz after resume, as you suggested :)
[10:00] <seb128> Ng, you got compiz to freeze after resume?
[10:01] <seb128> I'm wondering if I didn't get the same issue, my xorg was frozen after resume yesterday
[10:01] <Ng> seb128: yes, I tried several suspends over the course of the last couple of days and it happened every time
[10:02] <Ng> I've had one crash where X was completely dead after resume, but the other times it was just compiz and restarting it blindly with alt-f2 (at the suggestion of hyperair) resurrected things
[10:02] <seb128> I got it twice so far but I didn't suspend a lot since I upgraded
[10:02] <Ng> I suspend at least twice a day ;)
[10:02] <seb128> thanks for the hint in any case
[10:02] <seb128> I suspend often but I just came back from vac
[10:02] <seb128> and I had alt-tab freezing compiz issues so I downgraded thing for a while
[10:03] <seb128> until a fixed linux deb came to test which fixes that
[10:03] <tseliot> Ng: did you file a bug report about the regression in mesa?
[10:03] <seb128> and yesterday I noticed the suspend issue
[10:03] <Ng> yeah that stuff is weird, I've not seen any other compiz hangs from alt-tab or whatever, it was just resume
[10:03] <Ng> tseliot: bryce seemed to think it was one that's already filed, but I'll happily file another
[10:04] <tseliot> Ng: ok, if bryce said so, I'm sure it was already filed ;)
[10:05] <Ng> I hope it's an easy fix somewhere, X has been almost perfectly stable in karmic otherwise for me. I think I've had maybe 3 actual real hangs since I upgraded weeks and weeks ago, until this mesa thing
[15:44] <tormod> bryce: I wonder if ati KMS is fscked in stock Karmic, see bug 410058
[15:47] <tormod> maybe we need to push a new libdrm anyway and rebuild the -ati. see xorg-edgers for a libdrm 2.4.13.
[16:05] <tseliot> tormod: do you refer only to libdrm-radeon1 or also to the drm in the kernel?
[16:06] <tormod> in the kernel?
[16:06] <tseliot> yes
[16:08] <tseliot> so you were referring to the user space component
[16:09] <tormod> gotta run!
[16:14] <Q-FUNK> would anyone remember which file in X server core defines PCI manufacturers with individual video drivers?
[16:16] <Q-FUNK> öö.. defines the match between ID and driver
[16:16] <jcristau> hw/xfree86/common/xf86<mumble>.c
[16:17] <jcristau> also, grep.
[17:13] <Q-FUNK> jcristau: would you have a minute to examine a patch?  my C skills *are* limited and your guidance would be appreciated.
[17:13] <jcristau> not right now, sorry
[17:13] <Q-FUNK> ok
[17:14] <jcristau> but, email works.
[17:14] <Q-FUNK> ok, I'll do that
[17:17] <Q-FUNK> jcristau: sent.
[19:12] <jcristau> Q-FUNK: not sure what's the point of including amd in there
[19:13] <Q-FUNK> mostly for backward-compatibility.
[19:13] <jcristau> looks fine otherwise
[19:13] <Q-FUNK> not essential, though, indeed
[19:13] <jcristau> backwards compat with what? a driver that doesn't support current servers? :)
[19:14] <Q-FUNK> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/423866
[19:14] <Q-FUNK> hmm.. good point :)
[19:14] <Q-FUNK> I've attached a simpler patch for X 1.4 there, also
[19:14] <Q-FUNK> and a slightly cleaner version of what I mailed you
[19:15] <Q-FUNK> bug #423866
[19:15] <Q-FUNK> erm... right
[19:20] <Q-FUNK> jcristau: I also just noticed that cyrix and nsc no longer ship with ubuntu.  we'd probably need to skip that part of the changes.
[19:21] <Q-FUNK> do I assume that whatever wasn't matched by a specific driver in that file falls back to vesa?
[19:21] <jcristau> yeah
[19:24] <Q-FUNK> right, so in that case we'd only need the GX2 part added
[21:24] <mac_v> bryce: for Bug 397839 , you added the ATI in the description , is it because it is *now* not fixed in ATI alone ?
[21:24] <CShadowRun> hi, my friend told me that he configured his multi display setup with ubuntu's built in config, on an nvidia card, i assume that means nvidia and xrandr play nice in karmic?
[21:25] <bryce> mac_v, no it's an automatic script that adds that stuff to bug descriptions.  No particular significance to that.
[21:26] <mac_v> oh ;) ... thanks
[21:30] <mac_v>  i have a doubt about the $xset command.... i was using $xset s 300 for the screensaver problem , now i'm not sure how to reset the time to default , $xset reset is for something different, do i just to an $xset s 600 ?
[21:35] <tormod> mac_v it is reset if you log out
[21:38] <mac_v> tormod: hmm... but previously the screen blanking bug was occurring at 10 mins but after i used the xset command it started happening at 5mins , so i thought this was the cause...
[21:38] <mac_v> good to know i didnt mess up ;)
[21:38] <mac_v> thanks
[21:39] <bryce> yeah the blanking (or non-blanking) bug still persists.  power management seems really screwed up on my hardware
[21:41]  * mac_v started having burn-ins :(
[21:44] <tormod> power management is spread out between way too many packages and independent developers...
[22:17] <Q-FUNK> bryce: do you think that we could get the patches at bug #423866 merged for at least karmic?
[22:23] <bryce> Q-FUNK, comment #5 implies the patch was updated but isn't attached.
[22:25] <Q-FUNK> bryce: erm. right. correct.  any tool you can recommend to refresh the patch in a more efficient manner than copying the original all over again, patching that, removing the extraneous content, then diffing again?
[22:25] <bryce> that sounds like about how I'd have to do it
[22:26] <Q-FUNK> quilt seems ot be able to perform all sorts of backflips on patches, but I haven't quite figured out how to use it.
[22:27]  * bryce nods
[22:27] <hyperair> man quilt!
[22:28] <hyperair> i only ever use push, pop and refresh though
[22:28] <hyperair> and add
[22:37] <Q-FUNK> bryce: updated
[22:38] <Q-FUNK> bryce: I might still add nsc and cyrix to the 1.4 patch for Hardy, but the 1.6 patch can pretty much go as-is for karmic.   for jaunty, it can go too, but it would have to go in at the same time as a geode with cherry-picked GX2 fixes.
[22:40] <Q-FUNK> I'm currently narrowing down what could be the bare minimum changes we'll need to apply to -geode in jaunty before we can safely apply that X server patch.  
[22:42] <Q-FUNK> in karmic, though, we already have the latest upstream geode, which no longer crashes on GX2 hardware.