[08:58] <tjaalton> RAOF: whee, you found the commit to fix the mesa assert?
[08:58] <tjaalton> I was told that the assert itself was unnecessary, but that there probably was something to it
[09:06] <tjaalton> nouveau dri hasn't crashed on me during the weekend.. helps if the window count is kept low
[09:07] <tjaalton> but can't understand why links from TB don't work on my desktop, laptop is fine
[09:07] <tjaalton> (ffox opens them as 'www.%u.com')
[09:14] <RAOF> tjaalton: You're after the nv50 hunk of 7401590de for the mesa assert.
[09:15] <RAOF> Which, piglit pending, should totally be nominated for 7.10
[09:21] <hyperair> hi. where can i find xrandr's C functions documentation?
[09:22] <hyperair> that monolithic manpage isn't bringing me anywhere
[09:22] <jcristau> read the protocol spec
[09:22] <jcristau> the libXrandr api is a thin wrapper around that.
[09:22] <hyperair> hmm okay
[09:22] <hyperair> but what about the strange datatypes that it returns?
[09:23] <hyperair> all i'm trying to do is get the current resolution
[09:23] <jcristau> like what?
[09:23] <hyperair> of individual outputs
[09:23] <hyperair> XRRScreenConfiguration*
[09:23] <hyperair> XRRScreenSize*
[09:23] <hyperair> yeah, stuff like that
[09:24] <jcristau> what's strange about a struct?
[09:24] <hyperair> oh wait a sec, the structs are documented!
[09:24] <hyperair> =O
[09:24]  * hyperair facepalms
[09:27] <tjaalton> RAOF: ah, cool.. will check
[09:27] <RAOF> hyperair: :)
[09:43] <hyperair> RAOF: are the stuff mentioned inside XRandr(3) all the functions i can use? the protocol document seems to mention some other stuff..
[09:43] <hyperair> like RRGetOutputInfo and the like
[09:43] <jcristau> no, the manpage wasn't updated after 1.1
[09:44] <RAOF> hyperair: I'd be looking at the protocol doc in x11proto-randr-dev
[09:44] <hyperair> oh okay.
[09:44] <jcristau> and <X11/extensions/Xrandr.h>
[09:44] <hyperair> thanks.
[11:07] <klattimer> Does anyone have any ideas about this bug; https://bugs.launchpad.net/compiz/+bug/718663
[11:07] <ubot4> Launchpad bug 718663 in xserver-xorg-driver-vesa (and 2 other projects) "Blank unity desktop (affects: 1) (heat: 8)" [Undecided,New]
[11:09] <jcristau> not enough info there.
[11:11] <tjaalton> yep, best to use 'ubuntu-bug' when filing a new bug
[11:11] <tjaalton> there are three "upstreams" marked for that bug
[11:12] <tjaalton> or projects, none of which is ubuntu
[11:18] <klattimer> tjaalton: ah :/ 
[11:18] <klattimer> what info do you need?
[11:24] <tjaalton> klattimer: please run 'apport-collect 718663'
[11:25] <tjaalton> it'll attach relevant information to the bug
[11:25] <klattimer> tjaalton: done
[11:26] <klattimer> this'll take a minute
[11:27] <tjaalton> hmm does it have a poulsbo in it?
[11:27] <tjaalton> guess we'll see
[11:27] <tjaalton> ah no
[11:28] <klattimer> tjaalton: sorry I'm having trouble with apport now :/
[11:29] <klattimer> running it as user works but fails to collect log files, running it as root tells me gtk couldn't be initialised 
[11:29] <klattimer> :/
[11:29] <tjaalton> it should ask for your password
[11:29] <tjaalton> to collect the logs
[11:30] <klattimer> tjaalton: that doesn't happen :/
[11:30] <tjaalton> wait, you're on 10.10?
[11:31] <tjaalton> aka maverick
[11:31] <klattimer> tjaalton: nope natty
[11:31] <klattimer> ah, it appears gdm was causing problems 
[11:32] <tjaalton> then you don't have all the updates
[11:32] <klattimer> hmm
[11:32] <tjaalton> since xserver-xorg should be 1:7.6~3ubuntu4
[11:32] <klattimer> I just updated this morning 
[11:32] <tjaalton> from maverick?
[11:32] <klattimer> tjaalton: no on natty
[11:32] <klattimer> this is a natty install 
[11:32] <klattimer> right through 
[11:32] <klattimer> I'm working on indicator-datetime (contracted) 
[11:32] <klattimer> so I need to use natty 
[11:33] <tjaalton> ok so what does 'apt-cache policy xserver-xorg' show as the installed version?
[11:33] <klattimer> installed 7.5, candidate 7.6
[11:33] <tjaalton> see
[11:34] <klattimer> hmm, maybe something was a little wrong during the update
[11:34] <klattimer> thanks tjaalton
[11:34] <tjaalton> how did you upgrade?
[11:35] <klattimer> tjaalton: apt-get update, apt-get upgrade 
[11:36] <klattimer> but it seems all of the xorg stuff was either half installed, or not installed 
[11:36] <klattimer> maybe something went wrong during the upgrade
[11:36] <tjaalton> it refuses to remove packages
[11:36] <tjaalton> so doesn't always work during the devel phase
[11:38] <tjaalton> use dist-upgrade or update-manager..
[11:39] <klattimer> tjaalton: thanks ;)
[13:50] <gordboy> so why are x-swat/x-updates offering a beta nvidia driver (that doesn't work properly) when their mission statement says they offer *stable* upsteam ? it would be very nice if you offered 260.19 nvidia driver, instead
[14:00] <tseliot> gordboy: maybe because they're supposed to work with the new Xserver with the IgnoreABI option. I don't have a real answer for you though
[14:03] <gordboy> tseliot: interesting. if that were the case, then why are the xorg-edgers (the bleeding cutting edge, break your system weekly ppa) offering the stable driver ? seems to me there is a bit of confusion ...
[14:04] <tseliot> gordboy: I wouldn't know, maybe 270.18 was really meant to be uploaded to xorg-edgers instead
[14:12] <ricotz> bjsnider, ^^^ ;)
[14:20] <tjaalton> klattimer: so do things work better after the upgrade?
[14:21] <tjaalton> klattimer: all that the logs reveal is that compiz had segfaulted three times
[14:21] <tjaalton> the x log was fine
[14:27] <tjaalton> hmm, I take that back, the xserver had crashed as well
[14:32] <bjsnider> gordboy, what distros is this?
[14:35] <gordboy> bjsnider: lucid
[14:35] <gordboy> i know maverick had trouble with 260 and the NVRM: os_raise_smp_barrier(), invalid context! thing. but lucid doesn't
[14:36] <bjsnider> well, i uploaded the 270 blob because nvidia doesn't generally break things retroactive to previous x-servers. it works fine here on maverick
[14:37] <klattimer> tjaalton: yeah thanks
[14:37] <klattimer> you can close the bug
[14:38] <tjaalton> klattimer: cool
[14:40] <gordboy> bjsnider: ok. well just so you know, the 270 on lucid gives freezes and full log files. the 260 is fine. tested on 8500gt, 9500gt and ge210
[14:40] <bjsnider> alright, well if i were you i'd go back to using the standard lucid driver
[14:42] <gordboy> bjsnider: the problem with that, is that flash 10.2 crashes immediately with 195, and libvdpau1. i know this is an inexact science ...
[14:42] <bjsnider> yeah but thi is above our pay grade
[14:43] <bjsnider> we can't fix closed-source flash and a binary graphics driver
[14:43] <bjsnider> at some point we have to throw up our hands and bow to the absurd
[14:43] <gordboy> point taken. but the 260 works well with lucid, and is the current stable offering. just saying
[14:43] <jcristau> then use that?
[14:44] <gordboy> the only place to get it is from xorg-edgers :)
[14:45] <jcristau> or nvidia.
[14:46] <bjsnider> gordboy, it works well for _you_ in lucid. i could probably scare up a dozen bug reports from others who say it causes problems for them
[14:48] <gordboy> i'll trade my 3 definites for your dozen maybes, any day :)
[15:15] <bjsnider> tseliot, i submitted a bug about some packaging issues with nvidia-current, as you requested
[15:16] <bjsnider> 704607
[15:16] <tseliot> bug 704607
[15:16] <ubot4> tseliot: Bug 704607 on http://launchpad.net/bugs/704607 is private
[15:16] <bjsnider> what?
[15:17] <tseliot> bjsnider: thanks for reporting. I'm working on nvidia today so I should fix it now in my git branch
[15:18] <bjsnider> very trivial changes. easy to implement
[15:19] <bjsnider> tseliot, i also created a bug about moving the nvidia preinstall script to jockey-common from nvidia-common. can you tell pitti about it? i don't think he was alerted it's bug 704597
[15:19] <ubot4> bjsnider: Bug 704597 on http://launchpad.net/bugs/704597 is private
[15:21] <tseliot> bjsnider: oh, right the hook for the installer. Thanks for reminding me about it. I'll talk to pitti
[15:22] <bjsnider> good, because i don't know what channels he's in
[15:43] <thesheff17> RAOF: ping.....I finally believe I got the backtrace  from the crash through gdb. http://pastebin.com/Hc19Q0fg not sure if that helps at all but let me know if you have any ideas to fix it.
[15:45] <jcristau> well, fglrx.
[15:50] <thesheff17> jcristau: yea I know...I'm really looking for a 4 port video card PCI-express that supports up to 4 monitors without breaking the bank. I got this ATI FirePro 2450 512MB PCI-e x16 Graphics Video Card for about 150 off ebay :-/  
[17:13] <kklimonda> hey, does nouveau in natty support power managment?
[17:17] <Sarvatt> kklimonda: http://nouveau.freedesktop.org/wiki/PowerManagement
[17:20] <kklimonda> Sarvatt: btw, I've had a problem with Firefox causing X to use 100% of cpu (pretty much halting everything) when I browsed google images, or other pages with a lot of images using nouveau. Any idea what would cause it? That was the reason I went back to nvidia
[17:23] <kklimonda> so, from the matrix is seems that there is some power managment for nv50, as long as I don't have a fan connected to it? :)
[17:25] <Sarvatt> it could be a lot of things :( have you been able to narrow it down any? only happen with compiz or something like that?
[17:25] <Sarvatt> kklimonda: no fan speed adjustment control which isn't a big deal since your laptop doesn't have a separate fan
[17:25] <kklimonda> Sarvatt: no, but it did happen every time.
[17:25] <kklimonda> Sarvatt: I think I didn't run compiz
[17:26] <kklimonda> I could check it - it should be simple test :)
[17:26] <ricotz> Sarvatt, hi :)
[17:27] <Sarvatt> hiya! whats up ricotz?
[17:27] <ricotz> i wanted to play a bit with wayland
[17:27] <ricotz> Sarvatt, do you think pixman 0.21.4 would be considered for a sync?
[17:27] <Sarvatt> oh yeah we need a cairo-gl in xorg-edgers
[17:28] <ricotz> Sarvatt, is it? the current cairo package builds its gl extension?
[17:28] <Sarvatt> ricotz: really I've been torn on that, I dont think 0.21.x is a good idea for natty since 0.22 wont be out and its the development branch but 0.21 already went into unstable.. was hoping to put the stable 0.20.x in unstable once squeeze released
[17:29] <jcristau> yeah a development snapshot in natty doesn't seem like a good plan
[17:29] <ricotz> Sarvatt, there was a 0.20 release in exp once, perhaps this one can be pulled
[17:30] <Sarvatt> it didn't build on our toolchain until that -O2 bug got fixed in our GCC a few weeks ago so we couldn't sync it then
[17:31] <ricotz> ok, but isnt this package saved somewhere?
[17:31] <Sarvatt> ricotz: also waiting for notify-osd to get updated to not be screwed up with the newer pixman, I pinged MacSlow about it
[17:32] <Sarvatt> ricotz: well it's already up to 0.20.2 upstream and that never had a debian release
[17:32] <Sarvatt> https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/654921
[17:32] <ricotz> so making an ubuntu only version of it, is no option?
[17:32] <ubot4> Launchpad bug 654921 in notify-osd (Ubuntu) "Black border in the notifications when effects are turned off (affects: 10) (dups: 1) (heat: 68)" [Undecided,Confirmed]
[17:34] <Sarvatt> ricotz: thats pretty much our only option besides staying at 0.18.4 and losing out on all the arm speedups :D
[17:35] <ricotz> so should be worth it ;)
[17:39] <ricotz> Sarvatt, i will do it
[17:39] <Sarvatt> ricotz: awesome, thank you for doing that!
[17:41] <jcristau> i'm wondering if i should get pixman 0.20 into testing
[17:54] <ricotz> Sarvatt, http://people.ubuntu.com/~ricotz/pixman/
[18:02] <ricotz> jcristau, are you going to do an upload to testing?
[18:03] <jcristau> i don't know yet.
[18:04] <ricotz> next debian release can probably wait for 0.22 
[18:16] <Sarvatt> kklimonda: firefox directly from mozilla might be worth testing, they bundle their own pixman in that one and nouveau+pixman 0.18.x have had problems specifically with google image search in the past
[18:17] <kklimonda> Sarvatt: ok, I will test it out tomorrow
[18:18] <Sarvatt> https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/608613 i'm looking at you
[18:18] <ubot4> Launchpad bug 608613 in pixman (Ubuntu) "Nouveau tiling problem with firefox (affects: 2) (heat: 17)" [Undecided,Fix released]
[18:19] <Sarvatt> they use their own heavily patched cairo too
[18:32] <ricotz> Sarvatt, do you if natty will ship the needed firmware for nouveau 3d support of nvc0?
[18:32] <Sarvatt> ricotz: very much doubt it
[18:32] <ricotz> Sarvatt, hmm :(
[18:32] <Sarvatt> I dont even know how to get it at the moment, its actual code from the blob so I doubt we could ever ship it :(
[18:33] <Sarvatt> I believe*
[18:54] <bryceh> thesheff17, what bug # is this for?
[18:56] <Sarvatt> ricotz: wonder if its in here - https://github.com/pathscale/envytools/
[19:00] <ricotz> Sarvatt, yeah, i found that, there are the tools to get ;)
[19:06] <thesheff17> bryceh: I was working with RAOF to troubleshoot this problem...I haven't filed a bug yet.  It is completely random about every 48 hours with that ATI FirePro 2450 card.  Do you want me to file a bug?
[20:38]  * penguin42 isn't too sure how to report a bug he's currently seeing - when windows appear they have junk in and then quickly get rendered a fraction of a second later; that's KDE on Radeon HD4350 open driver - any ideas for nailing it down?
[20:40] <jcristau> goes away when you turn off compositing?
[20:41] <penguin42> let me try - there appears to be a 'suspend desktop effects' button
[20:42] <penguin42> jcristau: No, harder to spot though because stuff is faster, but you can still see it
[21:48] <RAOF> thesheff17: Hm.  That looks like it's probably a fglrx problem.  The backtrace suggests that it's occurring when something is changing the cursor image, though, so that might help you reproduce it.
[22:02] <thesheff17> RAOF: ah ok...I will have to see if I can pin point it.  I wonder if it is only happening when it changes over a certain app running...maybe chrome
[22:03] <RAOF> Something like that would seem likely.
[22:03] <RAOF> I think the time has come to file a bug on fglrx with that backtrace attached.
[22:04] <RAOF> The backtrace makes it look like it really is a fglrx bug, so it's not likely to be fixable by us, but I understand that the amd guys check launchpad every now and then.
[22:05] <thesheff17> RAOF: sure will do...it isn't horrible since it only happens every 48 hours or so. should I use these steps to report a bug? https://wiki.ubuntu.com/X/Reporting
[22:07] <RAOF> thesheff17: Yes, please.  For you, the main thing to attach will be that backtrace.
[22:07] <thesheff17> RAOF: ok sounds good.
[22:08] <thesheff17> RAOF: Thanks for the help.
[22:12] <RAOF> No problem!
[22:16] <thesheff17> RAOF: not that this would have anything to do with the bug but so I have 2x2 monitors.  The top two monitors I cannot drag applications through the top two monitors.  but I can drag an app down to the bottom monitor and then over to the other one and then up to the other monitor. Does that make sense?
[22:18] <RAOF> That does make sense, but it might be a fglrx quirk?  There's no X-y reason why you shouldn't be able to have a rectangular array of outputs.
[22:18] <thesheff17> RAOF: yea not a huge deal just another strange thing I ran into.
[23:23] <afiestas> Hey, my X's (or maybe the kernel, I'm not sure) are crashing a looooot in Natty
[23:23] <afiestas> how can I provide more debug info?
[23:24] <afiestas> it happens randomly when I use Xv (via mplayer/vlc/whatever)
[23:24] <penguin42> afiestas: What graphics card?
[23:25] <afiestas> penguin42: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (pr
[23:25] <penguin42> ok, so it starts up, just sometimes dies?
[23:26] <afiestas> it crashes when I use Xv (the X video accelerator api)
[23:26] <afiestas> via Kamoso (Webcam app) Vlc mplayer etc
[23:26] <penguin42> how does it crash? Does the whole thing lock up? Does it log out? Does it draw aliens?
[23:27] <afiestas> it stop refreshing, and after a few seconds everything turns black
[23:27] <afiestas> I can't switch to any tty, but if for example I'm watching a film I still can hear the sound
[23:28] <penguin42> can you ping it?
[23:28] <afiestas> mm no idea, but I can try the next time
[23:28] <afiestas> also I can leave sshd open and get info if needed
[23:29] <penguin42> yeh, so look for any errors at the bottom of dmesg, and also look for the errors at the end of /var/log/Xorg.0.log
[23:30] <afiestas> ookiz, I'm going to do some patche for Kamoso now (webcam application) so I will reproduce it hopefully
[23:33] <RAOF> afiestas: Hm.  Does the apport hook trigger?
[23:34] <afiestas> RAOF: mm as far as I can tell, nope
[23:34] <afiestas> can I check it someway?
[23:35] <RAOF> You could ssh in and grab the error state.
[23:36] <afiestas> what is error state exactly? what I have to grab?
[23:38] <RAOF> The output of intel_gpu_dump and /sys/kernel/debug/dri/0/i915_error_state are good.
[23:39] <RAOF> If it's Xv related I could also throw up a testing package for you; there's a possible problem that may be what you're hitting.
[23:40] <afiestas> okz
[23:40] <afiestas> well I'm quite sure that it is Xv related
[23:40] <afiestas> it crashes only when I'm doing some video stuff
[23:42] <bryceh> afiestas, grab `dmesg` as well
[23:42] <afiestas> ookz
[23:47] <RAOF> Aha!  We have a candidate commit for the i965 gpu hangs.
[23:49] <bryceh> RAOF, if you mean ae8877e3, I'm already packaging it :-)
[23:50] <RAOF> Hm.  I means 23f9b1
[23:50] <RAOF> s/means/meant
[23:52] <bryceh> oh, then we have fixes for two gpu hangs, lovely
[23:52] <bryceh> ah wait, same patch
[23:53] <bryceh> gah I'm on crack
[23:54] <bryceh> RAOF, yes that's the commit I meant.  I'm also pulling in ae8877e3
[23:54] <RAOF> :)
[23:54] <bryceh> RAOF, why do you put up with me
[23:55] <afiestas> ue ue, package package! xD
[23:56] <afiestas> right now work on Video stuff in Natty is deadly xd
[23:56] <bryceh> RAOF, btw what are you working on at the moment?  Would you have time to look at recent commits to mesa?  jcristau said there were some cherrypicks worth including in ubuntu, but looks like I'm not going to get to them today
[23:57] <bryceh> RAOF, also we're a couple revs behind debian with mesa, although mostly looks like fixes for tangential stuff; still, might be nice to pull in anyway so we're up to date
[23:57] <RAOF> I'm currently looking at mesa; specifically unbreaking Unity on nv5x+.  I'll check out the cherry-picks.
[23:58] <bryceh> btw, I uploaded a fix to mesa earlier this morning
[23:58] <RAOF> Thanks.  I'll pull that in.
[23:59] <RAOF> Did jcristau happen to mention what cherrypicks were worthwhile, or just following the 7.10 branch?