[00:00] <Sarvatt> i *just* got libxfont
[00:00] <Sarvatt> shoot cant use apt-get either
[00:01] <bryce> grumble grumble
[00:01] <bryce> well, at least I did verify this time that 190 applies
[00:01] <Sarvatt> somethings majorly screwed up, i better reboot and hope for the best
[00:10] <johanbr> hmm... nouveau + all the other bits from xorg-edgers fails for me, "error opening the drm"
[00:11] <johanbr> http://pastebin.com/f2c14c96b
[00:11] <bryce> Sarvatt, luck?
[00:11] <Sarvatt> yeah just something screwy. latest intel git doesnt boot x though which was fun to find out :D
[00:12] <Sarvatt> Version: 7.0.16~git20091111.3ec82cd7-0ubuntu0sarvatt  Version: 7.0.15-1 for x11proto-core-dev, looks like the protos arent even built yet
[00:14] <Sarvatt> oh hey
[00:14] <Sarvatt> 190 actually applies to master now with your change
[00:14] <bryce> good
[00:14] <RAOF> Argh!  Why do I _still_ need to look up 'git help checkout' to switch to an upstream branch?
[00:20] <Sarvatt> shoot, auto-xorg-git changes coming back to bite me now that it was updated, i used ~ instead of + in alot of the protos and libs so >=1.2.0 build deps fail for 1.2.0~whatever
[00:25] <RAOF> Should I upload a new nouveau-kernel-source package to Lucid, or wait for whatever falls out of the kernel team discussions?
[00:26] <RAOF> Interesting context: nouveau is currently untestable on Lucid, because the current nouveau-kernel-source fails to build against 2.6.32 kernels.
[00:27] <bryce> RAOF, I'd doublecheck with the kernel team first
[00:38] <Sarvatt> oops, looks like 177_animated_cursor_change_master.patch needs to go too
[00:39] <Sarvatt> ../../render/animcur.c: In function ‘AnimCurDisplayCursor’:
[00:39] <Sarvatt> ../../render/animcur.c:222: error: ‘struct _DeviceIntRec’ has no member named ‘isMaster’
[00:57] <Sarvatt> thats on master but will be the same on 1.7 branch -- http://cgit.freedesktop.org/xorg/xserver/commit/?id=b12d302df8283186ce87882c29b2b0294adb2770
[00:59] <Sarvatt> darn http://paste.ubuntu.com/334210/
[01:06] <Sarvatt> yep 177 fails on 1.7.2 too
[01:08] <Sarvatt> checking if 190_cache-xkbcomp_output_for_fast_start_up.patch makes 1.7.2 fail to build now too like it does master
[01:09] <Sarvatt> pushing this little atom cpu hard tonight :)
[01:09] <bryce> hehe
[01:11] <bryce> hrm, wonder if there exists an updated version of 190
[01:11] <bryce> bugger my pbuilder environment still isn't updated
[01:12] <bryce> well, we can leave 190 disabled for alpha-1, that won't be the end of the world
[01:13] <bryce> ditto 177
[01:14] <Sarvatt> yeah i'm using edgers just to see if things work, had to change x11proto-xf86bigfont-dev (>= 1.2.0), to x11proto-xf86bigfont-dev (>= 1.1.99), to make it build because of 1.2.0~ behind lower than 1.2.0
[01:15] <Sarvatt> hmm 
[01:15] <Sarvatt> checking for DMXMODULES... yes
[01:15] <Sarvatt> ../configure: line 20715: XDMXCONFIG_DEP_CFLAGS: command not found
[01:15] <Sarvatt> ../configure: line 20716: C: command not found
[01:15] <Sarvatt> ../configure: line 20717: XDMXCONFIG_DEP_LIBS: command not found
[01:15] <Sarvatt> ../configure: line 20718: linker: command not found
[01:15] <Sarvatt> (sorry for so many lines at once)
[01:17] <Sarvatt> 1.7.2 failed the same as master with 190 applied :(
[01:17] <jcristau> Sarvatt: that's fixed in 1.7.3
[01:18] <jcristau> that doesn't fail the build here tho
[01:18] <Sarvatt> yeah doesnt fail, just saw the error while that one was building
[01:19] <Sarvatt> same failure on 1.7.2 with 190 though http://paste.ubuntu.com/334216/
[01:25]  * bryce comments out in git
[01:25] <bryce> it's my fault, I said "190 was easy" earlier and jinxed us
[01:39] <Sarvatt> now its failing in hw/xfree86/common/xf86Events.c :(
[01:40] <Sarvatt> patch 135
[01:41] <Sarvatt> trying 1.7.2 to see if it fails there too
[01:41] <Sarvatt> gotta love ccache
[01:42] <Sarvatt> http://paste.ubuntu.com/334223/
[01:44] <RAOF> Ok.  So, nouveau would also like libdrm 2.4.16 for Lucid.
[01:45] <Sarvatt> intel requires 2.4.16 to build now too
[01:45] <RAOF> And it looks like it's practically finished in pkg-xorg git.
[01:48] <Sarvatt> darn, ccache doesnt work when you build 2 seperate versions of the same package :D
[01:56] <Sarvatt> and i'm an idiot.. disabled 135 when i built 1.7.2 to see if 135 made it fail that time :D
[02:05] <Sarvatt> yeah 135 fails on 1.7.2 in origin/ubuntu too :( http://paste.ubuntu.com/334228/
[02:05] <Sarvatt> builds fine without it
[02:08] <Amaranth> oh yeah, can we drop the XAA hack now? I don't think any driver that supports compiz uses XAA by default anymore
[02:08] <Amaranth> I can't drop the compiz half of it until the Xorg half is gone
[02:10] <bryce> which XAA hack is this?
[02:10]  * Amaranth looks for it
[02:10] <bryce> the radeon XAA hack for low mem cards?
[02:10] <Amaranth> it was a way to dynamically enable XaaNoOffscreenPixmaps
[02:11] <Amaranth> from way back in feisty or something
[02:11] <Amaranth> looks like maybe it's gone already
[02:11] <Amaranth> I know it wasn't some time during karmic development though
[02:12] <bryce> if you spot it, let me know
[02:12] <bryce> we mostly don't care about XAA anymore
[02:12] <Amaranth> well nothing in debian/patches mentions _COMPIZ_GL_INCLUDE_INFERIORS anymore so I guess it is gone
[02:13] <bryce> Amaranth, there actually is a situation where XAA is used on -ati
[02:13] <bryce> upstream found that on some antique cards they can't do EXA very well so they do XAA by default on them
[02:14] <Sarvatt> they'd have to be crazy to be using compiz in that situation where they have 32mb or under video ram though lol
[02:14] <Amaranth> those are the same ones that report invalid GL_MAX_TEXTURE_SIZE, aren't they?
[02:14] <bryce> however from what I've seen and heard this causes as much trouble as it solves, and I'm tempted to just force it all EXA anyway, and deal with the EXA bugs
[02:15] <bryce> Sarvatt, what our users crazy?
[02:15] <Amaranth> that need KMS to do it properly because they create a buffer large enough to fit the screen when rotated so they run out of memory
[02:17] <Sarvatt> doesn't fglrx use XAA still? I dont use it but thought it did for some reason
[02:18] <Amaranth> Pretty sure they have almost useful XRender acceleration so I don't think so
[02:19] <Sarvatt> thats the most positive comment about fglrx 2d acceleration i've ever heard
[02:21] <Sarvatt> wow 1.7.2 has a _huge_ load of dmx compile warnings, no wonder they rushed out 1.7.3
[02:22] <Amaranth> Well, fglrx is almost faster than software :)
[02:30] <Sarvatt> how many times is this darn xserver compile going to run the tests
[02:32] <Sarvatt> ...answer is 2
[02:37]  * Amaranth stabs xmodmap
[02:38] <Sarvatt> yep fully compiles fine without 135_rethrow_signals.patch. not the full build log because my scrollback didnt go back far enough: http://sarvatt.com/downloads/xserver_1.7.2_buildlog.txt
[02:38] <Sarvatt> not the same build environment that is going to be in lucid as soon as the stuff builds though of course
[02:58] <Amaranth> bryce: Should I turn on the compiz reflection plugin to test your GPU wedge hook? :)
[03:01] <Sarvatt> patches.ubuntu.com doesnt have the extracted patch folders anymore? :(
[03:06] <Sarvatt> hmm, guess it isnt that big a deal not having the apport hooks in the edgers packages but i need to add a hook for the intel-gpu-tools recommends update
[03:07] <Sarvatt> intel hasnt been stable upstream in almost a month now, i'm still having to use ones checked out on 11-11
[03:10] <Sarvatt> oh wait its 11/06, forgot i reverted back and dated it higher so it'd override the broken ones even then
[03:13] <Sarvatt> 2.9.99.901 release is ok except I cant use it on a 2.6.31 kernel without it killing x randomly, and cant suspend without the flickering problems under 2.6.32 on any 2.9.x release
[03:46] <Sarvatt> hmmm so what all do I need for this new udev driven xserver? i see synaptics in experimental has a udev rule installed with it, need to do anything special with evdev?
[03:48] <Sarvatt> oh theres a ubuntu branch for evdev now? sweet
[03:49] <Sarvatt> ubuntu did it different than debian before where hal installed the evdev fdi so i wasnt sure if udev installed an evdev rule or something like that
[04:13] <Sarvatt> lets see how this udev xserver works now. when I dont come back things blew up horribly :)
[04:15] <Sarvatt> i'm always disappointed when things just work :D
[04:17] <Sarvatt> was I supposed to purge hal first?
[06:02] <tjaalton> bryce: yeah I don't think the protos/libs are all built and published yet
[06:03] <tjaalton> Sarvatt: good catch on that merge goof, I forgot to add the VCS bits back
[06:07] <Sarvatt> the publisher is screwed up or something, even ppa builds arent getting published even though they say they have been and the protos built 6 hours ago https://edge.launchpad.net/ubuntu/lucid/i386/+builds?build_text=&build_state=all
[06:07] <tjaalton> yes, well LP has been down for hours
[06:07] <tjaalton> and been up maybe an hour or so
[06:08] <tjaalton> ah, those have been built fine, so it's the publisher alright
[06:09] <Sarvatt> x11proto-xf86bigfont built about 45 minutes ago on edgers and it still isnt getting used building server
[06:10] <Sarvatt> watched it turn into a gear then finish getting published but still not up for download either
[06:17] <Sarvatt> hmm looks like xfonts-utils is missing in the server build deps
[06:18] <Sarvatt> failed on the PPA configure.ac:41: error: must install fontutil 1.1 or later before running autoconf/autogen but its got font-util 1.1.1 in the PPA
[06:21] <Sarvatt> might be a xserver master only problem though
[06:54] <tjaalton> 1.7 doesn't check fontutil at all
[07:03] <Sarvatt> well its starting to update, x11proto-xinerama is breaking gtk app builds ;D
[07:14] <Sarvatt> hmm libx11 didnt get synced
[07:16] <Sarvatt> someone just hit rebuild on all the dep wait libs at the same time, of course it's going to fail :D
[07:44] <tjaalton> well, there are errors too
[07:44] <tjaalton> since the headers were moved...
[07:44] <tjaalton> although it shouldn't have mattered
[07:45] <tjaalton> if the deps were right, the packages would have been waiting in the depwait queue
[07:48] <tjaalton> stupid g-t can't open urls with epochs :)
[07:49] <tjaalton> Sarvatt: ok, maybe the build-deps should have been versioned, seems like four packages failed to build because the old version was available
[07:50] <tjaalton> Sarvatt: and libx11 can't be synced
[07:50] <tjaalton> if we are going to keep the la_AU stuff
[07:56] <tjaalton> so there are a couple of libs that need to bump the build-dep on libxext-dev
[07:57] <tjaalton> we are fine though, since the builds can be retried later
[08:28] <hyperair> Sarvatt: it seems that X segfaults when changing resolution on i965..
[08:28] <hyperair> using xorg-edger
[08:29] <hyperair> 3: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_set_pixmap_bo+0x4b) [0x7fda715b2d6b]
[08:29] <hyperair> 4: /usr/lib/xorg/modules/drivers//intel_drv.so [0x7fda715c0f7d]
[08:30] <hyperair> weird that it's calling an i830 function
[08:30] <hyperair> hmm there's a new x-x-v-intel around so i'll just upgrade and see
[08:33] <tjaalton> bryce: so, some libs failed to build because our libxext was newer than what the xextproto was set to Breaks. Once the synced libxext is everywhere, I'll order a round of rebuilds for the missing libs (four of them)
[09:02] <hyperair> ...this has to be the first time i've ever seen X screw up so bad i can't even use a terminal
[13:24] <paran> is this the right place to report problems with packages from xorg-edgers ppa?
[13:25] <tjaalton> if the guilty are here
[13:35] <paran> tjaalton: fair enough
[13:36] <tjaalton> tormod and Sarvatt are the ones you want
[13:36] <tjaalton> tormod is missing atm
[13:37] <paran> Sarvatt should be the guilty one in my case... Or, probably intel upstream
[13:38] <paran> I tried the latest intel packages (2.9.99.901+git20091202.a938673e-0ubuntu0sarvatt~karmic), too much glitches to even run a terminal windows
[13:39] <paran> characters only show up as black boxes, until I switch desktop back and forth
[13:40] <paran> gnome-terminal in a pretty much default karmic gnome installation
[13:46] <paran> the previous version 2:2.9.1~git-0ubuntu0tormod caused some corrupted fonts after suspend (not the same corruption), but was otherwise ok.
[13:47] <paran> also thanks a lot for the ppa-purge script, very useful :)
[15:35] <freeflyi1g> hi dudes, how to use thinkpad's trackpoint on karmic? 
[15:36] <freeflyi1g> I already configure it with gpointing-device-settings
[15:37] <freeflyi1g> X.0.log and lsinput output are here
[15:37] <freeflyi1g> http://paste.ubuntu.com/334564
[15:37] <freeflyi1g> http://paste.ubuntu.com/334565
[15:38] <freeflyi1g> tseliot: any clues?
[15:41] <tseliot> freeflyi1g: it should work just like a mouse, in relative mode, I guess
[15:42] <freeflyi1g> tseliot: I didn't get that lucky :)
[15:43] <tseliot> freeflyi1g: what's the problem?
[15:44] <freeflyi1g> tseliot: like scrolling can't be used
[15:45] <tseliot> tjaalton: ^^
[15:45]  * tseliot doesn't own a trackpoint
[16:28] <tjaalton> tseliot: can't check the urls now. xinput should work though
[16:29] <tseliot> does scrolling work with trackpoints?
[16:29] <tseliot> is it supposed to?
[16:36] <tjaalton> it's disabled by default
[16:37] <tjaalton> you need to hold a button down and then scroll
[16:38] <tjaalton> middlemouse by default
[16:42] <freeflyi1g> tjaalton: is there anything need to be done in kernel?
[16:42] <tjaalton> freeflyi1g: no
[16:43] <freeflyi1g> tjaalton: then trackpoint can't be detected here, I'm using lucid
[16:44] <tjaalton> xinput list, xinput list-props $id, xinput set-int-prop...
[16:44] <tjaalton> it doesn't work at all?
[16:45] <freeflyi1g> tjaalton: just the scrolling
[16:45] <tjaalton> so use xinput
[16:45] <tjaalton> to enble the property
[16:45] <tjaalton> +a
[16:50] <Sarvatt> darn libxinerama needs to publish already, cant build anything right now
[16:51] <bryce> tjaalton, aha.  did xextproto get fixed up?  anything I can do to help with this?
[16:51] <tjaalton> bryce: everything should be ready, but apparently libxinerama needs a retry?
[16:53] <Sarvatt> xinerama built fine
[16:53] <Sarvatt> https://edge.launchpad.net/ubuntu/+source/libxinerama/2:1.1-1/+build/1378080
[16:54] <Sarvatt> installing x11proto-xinerama-dev wanted to remove all of gnome dev packages too
[16:55] <Sarvatt> proto breaks the old libxinerama-dev version is all
[16:55] <tjaalton> I don't follow..
[16:55] <Sarvatt> hyperair: you and me both! intel git is so messed up right now
[16:59] <Sarvatt> libgtk2.0-dev tries to pull in libxinerama-dev
[16:59] <tjaalton> ok, so it's just a matter of time then
[17:00] <tormod> Sarvatt, I got libxinerama-dev 1.1 a few hours ago
[17:01] <tjaalton> bryce: the drivers might make it in debian this weekend (depends if there are people to upload them), which would allow us to sync them on monday
[17:01] <Sarvatt> ok both of the mirrors i use are screwy then, one didnt have the protos at all
[17:01] <tjaalton> gotta go again ->
[17:01] <bryce> tjaalton, ok
[17:02] <bryce> regarding xorg-edgers breakages... especially this cycle we probably should encourage people to look to upstream when they run into issues
[17:02] <hyperair> Sarvatt: ..again, huh.
[17:02] <tormod> bryce, that's usually what we do when they use xorg-edgers
[17:03] <bryce> tormod, ok
[17:03] <hyperair> Sarvatt: well hopefully it'll get stable before the next release
[17:03] <Sarvatt> hyperair: yeah its like a year ago only worse this past month in intel git :D i'm still using a checkout from 11/06 since it was the last time things just worked
[17:04] <hyperair> Sarvatt: heh, i've gone back to using the one in karmic =D
[17:04] <Sarvatt> oh not using lucid then?
[17:04] <tormod> bryce, it's also the main reason for xorg-edgers :) when upstream says "so you have a bug - try latest git"
[17:06] <tormod> what's cool now is that with lucid A1 + xorg-edgers, you have pretty much everything latest git, kernel, mesa, xserver, drivers
[17:06] <Sarvatt> phew! the libxinerama problem was just a mirror problem, both of the ones I tried weren't updated
[17:06] <hyperair> Sarvatt: no, not using lucid. i think i'll wait until somewhere around alpha 2 or so before upgrading
[17:09] <tormod> Sarvatt, you might noticed libxinerama worked fine in xorg-edgers also :)
[17:09] <bryce> tormod, right, I was just concerned with the number of people coming here for help with xorg-edgers issues
[17:10] <bryce> concerned in the sense that I don't want Sarvatt wearing himself out!  :-)
[17:11] <tormod> bryce, well that's fine, so we know what's up and can tell them/upstream. as long as it does not get too busy in this channel :)
[17:12] <tormod> yes we don't want that!
[17:12]  * Sarvatt disappears for months again
[17:24] <Sarvatt> woohoo, took 6 reboots but I made it into X with the latest intel :D
[17:24] <tormod> Sarvatt, your 12-Add-libudev... does not apply against master?
[17:25] <Sarvatt> i have a hook to wget a refreshed one that does
[17:26] <tormod> yes, the wget'ed one does not apply, unless I am doing something stupid
[17:27] <tormod> yes I did ^
[17:27] <Sarvatt> phew
[17:28] <Sarvatt> was going to say, it was working 30 minutes ago when i uploaded a new xserver
[17:28] <tormod> I had the old version laying around, did you just change it?
[17:28] <Sarvatt> change what? the patch? nope havent touched it since last night
[17:29] <Sarvatt> ahh i've gotta run, 2 hours late to a job :D
[19:25] <Sarvatt> jcristau: the flashing on 2.6.32 is fixed in drm-intel-next for me. of course what fixed it i have no clue
[19:28] <Sarvatt> down to 7.4w idle power usage now from around 8.1 too. i just tried this out since drm-intel-next doesnt merge into 2.6.32 cleanly right now http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
[19:30] <jcristau> Sarvatt: ah.  would be nice to figure out what fixed it to get it into 2.6.32.x.. :)
[19:31] <Sarvatt> 31 possibilities there
[19:32] <jcristau> maybe i can try tomorrow.  need to work though, and right now i should get home..
[19:47] <tormod> drm-next in kernel-ppa, that's awesome! how come I missed that
[20:06] <tjaalton> tormod: are you a DD now?-)
[20:07] <tormod> tjaalton, no why?
[20:07] <tjaalton> tormod: ah ok, saw the intel-gpu-tools upload, but that was sponsored?
[20:07] <tormod> at my current rate of Debian development I can be a DD in like ten years I guess :)
[20:08] <tormod> yes, I am a co-maintainer ("uploader" which is kind of wrong name) of some packages
[20:09] <tormod> I am discussing with the radeontool maintainer also
[20:10] <tjaalton> heh ok. I guess we need a DD to upload the current stack to unstable, and the drivers once they are ready in git
[20:10] <tormod> starts with j and ends with cristau :)
[20:11] <tjaalton> too busy I hear :)
[20:11] <tjaalton> any DD, willing to do the job this weekend after everything is go, would do
[20:13] <tormod> did you ask bgoglin?
[20:16] <tjaalton> jcristau did, no reply so far. let's see how it goes :)
[20:16] <jcristau> i'm asking -release if that'd be ok with them, too..
[20:16] <tjaalton> great
[21:02] <bryce> tjaalton, anything I can help with on xserver 1.7 right now?
[21:03] <bryce> ideally it would be nice to get xserver 1.7 uploaded today, but if that's not looking possible I have some bug tool work for the desktop team I should get to
[21:11] <tjaalton> bryce: it wouldn't help much anyway, since all the drivers need a rebuild, and it's wise to do that as syncs from unstable
[21:12] <tjaalton> or less work anyway
[21:13] <tjaalton> I believe the uploads to unstable will happen this weekend
[21:13] <tjaalton> so we could sync on monday
[21:13] <bryce> mm
[21:13] <tjaalton> some drivers will remain broken though, like wacom an evtouch (which doesn't build against 1.7)
[21:13] <tjaalton> but that shouldn't matter much for a1
[21:14] <bryce> fair enough, although I'm off all next week (and wife has stated she's banishing me from the computer) so won't be able to assist
[21:14] <tjaalton> oh :)
[21:14] <pwnguin> as long as you mention it in the release notes
[21:14] <tjaalton> bryce: well, there shouldn't be much drama
[21:14] <pwnguin> (wacom, not vacation)
[21:15] <bryce> tjaalton, tseliot might be able to help on the wacom and evtouch issues, could you touch base with him about it?  At least, like pwnguin says, it should be mentioned in release notes
[21:15] <tjaalton> I thought evtouch is dead, evdev supports runtime calibration now..
[21:15] <tjaalton> wacom needs xf86-input-wacom, but ron hasn't packaged it yet
[21:22] <bryce> maybe it is; from the touchpad session at UDS I got the impression it still had its uses
[21:22] <bryce> however evdev was clearly the way forward, it just needs more hardware support
[21:28] <tjaalton> runtime calibration support was added recently, so maybe it was just features missing from evdev that kept evtouch around
[21:29] <bryce> mm
[21:32] <tormod> I remember recently some evdev bugs, and some people using evtouch instead, was it the eeetop maybe?
[21:36] <tormod> no that was 441408 which was fixed in evdev. I guess only older howto
[21:37] <tormod> howto's talk about evtouch
[21:39] <tjaalton> ron packaged wacom after all http://people.debian.org/~ron/wacom/
[21:40] <pwnguin> fast!
[21:40] <tormod> xf86-input-evtouch (0.8.8-0ubuntu7) came recently, with fixes for eeetop
[21:40] <tjaalton> well, I mailed him about the progress yesterday or so
[21:42] <tjaalton> tormod: that's just calibration quirks
[21:42] <tjaalton> same thing can be done for evdev, it's just a matter of deciding where
[21:42] <tjaalton> aiui quirks belong to the kernel
[21:43] <tormod> the fix yes, but why are these people using evtouch?
[21:43] <tjaalton> I believe ogra babbled about calibration once
[21:43] <tjaalton> don't know where we stand now
[21:47] <bryce> we talked about it at length in a session on UDS
[21:47] <bryce> ogra seemed extraordinarily depressed about the whole situation, but gave a ton of good info
[21:48] <bryce> we scoped out a plan for an updated calibration tool, although the blocker is finding someone to do the work (what's new)
[22:21] <tjaalton> bryce: yeah maybe it was about the fact that evtouch had a tool for that. it should be a lot easier to make one for evdev now
[22:24] <bryce> yeah that rings a bell
[22:24] <bryce> (in my swiss cheese memory)
[22:25] <tjaalton> hehe
[22:27] <tormod> RAOF, is it linux-nouveau-modules instead of nouveau-kernel-source now?