=== mac_v is now known as mac_v`afk
=== mac_v`afk is now known as `afk
=== mac_v is now known as mac_v`afk
=== mac_v`afk is now known as mac_v
=== mac_v is now known as mac_v_
[10:19] <apw> tseliot, yo!  know anything about how OSD displays things, specifically whether it might do any wierd grabs for the cursor or something to do its fadey poop?
[10:20] <tseliot> apw: sorry but I've never played with OSD code. MacSlow would be the right dev to ask about that
[10:25] <apw> tseliot, how does compiz know to grey out an application pane?
[10:26] <RAOF> When the application stops responding to the WM_PING message (or somesuch), IIRC.
[10:27] <apw> so the underlying question is what the heck is gnome-terminal doing which would be affected by notify-osd stopping dead in its tracks
[10:28] <tseliot> so when a bubble from notify-osd shows up, the terminal is grayed out?
[10:49] <AlanBell> anything I can do to help with bug 428769
[10:49] <ubottu> Launchpad bug 428769 in xserver-xorg-video-intel "compiz starts with a blank screen on a 2048x1152 monitor" [Undecided,Confirmed] https://launchpad.net/bugs/428769
[10:49] <AlanBell> if someone can point me where to look I will happily read the code and do some debugging
[13:35] <CShadowRun> Don't suppose anyone can help me isolate a memory leak in X?
[13:35] <CShadowRun> I have to reboot almost daily because Xorg uses 70, 80% of my 8GB memory
[13:36] <tjaalton> check with xrestop if it's some client using pixmem
[13:38] <CShadowRun> Nah, the highest is compiz with 53MB
[13:38] <CShadowRun> All: 136449K total
[13:39] <tjaalton> which version?
[13:39] <CShadowRun> the latest version in karmic
[13:39] <CShadowRun> (been like it for years though)
[13:40] <CShadowRun> xorg is 1:7.4+3ubuntu7
[13:42] <tjaalton> what driver?
[13:42] <CShadowRun> nvidia 185
[13:45] <tjaalton> try without compiz
[13:45] <tjaalton> or another driver
[13:45] <tjaalton> meaning !nvidia
[13:46] <CShadowRun> hehe ok, i'll have to try that at some point, i use ubuntu for gaming alot so switching nvidia off makes life difficult for me :)
[13:46] <tjaalton> sure
[13:47] <tjaalton> it's not that there aren't memleaks in the server, but it's likely just the driver doing it
[13:47] <tjaalton> and I don't know how to valgrind the xserver to find real leaks
[13:47] <CShadowRun> hehe
[13:48] <CShadowRun> If anyone does know how to do that, i assume it wouldn't be that hard to find, it'd be that big >4GB block of memory :P
[13:48] <CShadowRun> it's using 53.3% atm
[18:27] <Duke`> xserver-xorg-video-intel is broken again on karmic x86_64 (xorg-edgers' package of 25th november)
[19:24] <tormod> Duke`, it has been broken in git for soon 3 weeks, but I have rolled it out again to stir things up :)
[19:24] <tormod> they are working on it
[19:24] <Duke`> ok
[19:25] <Duke`> is it the bug I mentioned some weeks ago, on jaunty? (it has been fixed since then)
[19:26] <tormod> you were talking about https://bugs.freedesktop.org/show_bug.cgi?id=25031, not?
[19:26] <ubottu> Freedesktop bug 25031 in Driver/intel "rendering and color corruption since 14109abf" [Major,New]
[19:35] <Duke`> yeah it seems so
[19:45] <tormod> CShadowRun, did you see the "Troubleshooting server memory leaks" thread on xorg ML today?
[19:45] <CShadowRun> tormod: nope
[19:45] <CShadowRun> I know absolutely nothing about this stuff though, i was just hoping to gather enough so i could submit a bug report
[19:46] <tormod> it refers to a debian and fedora report
[19:46] <CShadowRun> :)
[22:53] <tormod> bryce, are you syncing or merging intel-gpu-tools? I just saw the MIR released, but no new package.