[01:46] <bryce> tjaalton: is there a workaround to get xserver to build?
[01:49] <wgrant> bryce: With the libdrm conflict?
[01:50] <bryce> yeah
[01:50] <wgrant> I downgraded it manually in my chroot, but I don't think there's any workaround for the buildds...
[01:50] <wgrant> Other than hunting kernel guys.
[01:52] <bryce> mm, according to bug 308387 it *should* be fixed
[01:52] <bryce> or worked-around at least
[01:53] <wgrant> Ah, very recently.
[01:54] <bryce> funny my pbuilder chroot failed since I'd just updated it...  retrying
[01:54] <bryce> wgrant: btw how was your flight home?
[01:54] <wgrant> It was good - fairly uneventful, though we almost missed the Sydney->Melbourne connection.
[01:54] <wgrant> Yours?
[01:54] <bryce> it was perfect; eerily so.  
[01:55] <bryce> short, no babies, no one in the seat next to me, no security line waits, etc.
[01:55] <bryce> hmm
[01:55] <bryce> dpkg: dependency problems prevent configuration of pbuilder-satisfydepends-dummy:
[01:55] <bryce>  pbuilder-satisfydepends-dummy depends on libdrm-dev (>= 2.3.1); however:
[01:55] <bryce>   Package libdrm-dev is not installed.
[01:55] <bryce> dpkg: error processing pbuilder-satisfydepends-dummy (--configure):
[01:55] <bryce>  dependency problems - leaving unconfigured
[01:55] <bryce> Setting up bsdmainutils (6.1.10ubuntu3) ...
[01:56] <wgrant> Oh, and the bus to the BART station didn't come, so we had to walk. That was inconvenient.
[01:58] <bryce> ahh now it's going
[02:00] <bryce> portland got hit by a snowstorm a day after I arrived home; about 10cm in some places, and streets are iced over
[02:01] <bryce> it was cold but sunny today, with the roads passable, so  we were able to get out and go to the market this afternoon.  But another storm's coming tomorrow morning so I think that'll lock us in the rest of the week :-)
[02:01] <superm1> i just got sent back home because my flight from AUS->ORD got canceled because of some snowstorm at ORD (probably remnants of what you saw bryce :))
[02:01] <bryce> superm1: wow
[02:01] <bryce> superm1: hey btw, you'd mentioned something early last week about a touchscreen machine or something that I needed to look at?
[02:02] <superm1> bryce, yeah, BenC is supposed to give it to you
[02:02] <superm1> bryce, he was using it all week at UDS
[02:02] <bryce> ah ok
[02:02] <superm1> it should have fully support by the kernel evdev driver.  the X driver is lacking though
[02:03] <bryce> I'm off next week, so probably won't get a chance to do much with it until january anyway
[02:03] <bryce> (unless it turns out to be something simple)
[02:03] <superm1> yeah that should be fine.  we're not rushing on it, but just want to make sure the support lands sometime by when jaunty is out since we'll have other products after jaunty using the same display
[02:03]  * bryce nods
[02:04] <superm1> i looked at it a little bit and with a few hackish quirks it looks like you can get the pen moving, but i dont know the code that well, and just wanted to see if i could get it that far before handing the hardware off
[02:04] <bryce> I just had a call with one of our oem guys about this; sounds like we're going to give touch good attention for jaunty
[02:04] <superm1> yeah by fixing the evdev driver rather than hacking on wacom everything should start to just work :)
[02:05] <superm1> (that is for non wacom displays)
[02:05]  * bryce nods
[02:07] <superm1> also whenever you've got it to a satisfactory functionality, mirco muller had an interest in it, so you'll be passing it on to him when it gets to that point probably
[02:08] <bryce> okay
[02:58] <bryce> tjaalton: ok fixed up the signal patch (bug 226668), and committed to git.
[03:27] <pwnguin> aww, nouveau is broke
[03:27] <pwnguin> well, missing
[05:08] <bryce> missing?
[05:24] <pwnguin> the modules thing is mia
[05:24] <pwnguin> linux-nouveau-modules
[05:43] <tjaalton> bryce: ok, excellent. I've now requested rebuilds of x86/amd64
[05:43] <pwnguin> tjaalton: fyi, i think wacom works in jaunty
[05:44] <tjaalton> pwnguin: nice
[05:44] <pwnguin> i sent a mail to the list, lemme know if you think i'm wrong ;)
[05:45] <tjaalton> I haven't tested it but if tom thinks it works.. :)
[05:45] <tjaalton> bryce: you marked xorg-server for release, did you upload it?
[05:46] <tjaalton> ah there it is
[05:46] <tjaalton> cool
[05:48] <bryce> yep
[05:51] <pwnguin> on a scale from 0 to finished, does anyone know where nouveau in jaunty is at?
[05:57] <bryce> pwnguin: 7E
[06:00] <pwnguin> =/
[06:01] <pwnguin> mostly, I'd like to know whether I'm doing something wrong or it's just too early to expect installable packages
[06:02] <bryce> what exactly is your question?
[06:02] <tjaalton> it should be installable on jaunty
[06:02] <pwnguin> The following packages have unmet dependencies: xserver-xorg-video-nouveau: Depends: linux-nouveau-modules but it is not installable
[06:02] <pwnguin> E: Broken packages
[06:02] <tjaalton> hmm ok
[06:09] <bryce> tjaalton: do you have an idea on that?
[06:10] <bryce> does -nouveau depend on kernel stuff?
[06:10] <tjaalton> sure, it needs newer drm stuff, so there's a package which builds those
[06:16] <tjaalton> I'm not sure which source package provides that though. the package description suggests to use module-assistant first
[06:17] <tjaalton> pwnguin: grab the package, drop the dep and test :)
[06:17] <pwnguin> heh
[06:18] <tjaalton> hmm no, the kernel doesn't have any version of the module
[06:19] <tjaalton> off to work ->
[06:43] <pwnguin> so was i really supposed to fiddle with the package and test again?
[06:56] <bryce> pwnguin: yeah
[06:57] <bryce> fwiw, -nouveau is not officially supported by us yet (we won't triage bugs against it this release for example)
[06:57] <bryce> we'll accept and upload fixes of course, but at this stage it's considered completely experimental
[07:05] <tjaalton> pwnguin: it'll refuse to work without the drm module
[07:07] <tjaalton> raof should know the state of the package, but he's not online atm
[07:49] <pwnguin> thats what i figured; i'll ping him later
[08:26] <bryce> tjaalton: bug 308410 could use your attention
[08:27] <tjaalton> bryce: expected, and rebuilding those wouldn't help much, since they don't work with the new xserver without force
[08:27] <bryce> tjaalton: could you comment on the bug about this?
[08:29] <tjaalton> done
[08:31] <bryce> heh, no more ctrl-alt-backspace on my dev box
[08:31] <tjaalton> -retro ftw!
[08:38] <bryce> fwiw, with all of today's updates my eaglelake box is working much better
[08:44] <tjaalton> good
[08:53] <tjaalton> bryce: heh, good move to delete the comments :)
[08:53] <tjaalton> from the spec
[08:54] <bryce> tjaalton: I moved them to the wiki page
[08:54] <tjaalton> ah
[08:54] <bryce> whiteboard != forum
[08:54] <tjaalton> yeah
[08:55] <bryce> we're going to get a *lot* of comments about this once people become aware of the change
[09:00] <tjaalton> sure, let them come
[09:10] <lool> tjaalton: Is there an upstream bug for intel not building against linux' drm headers?
[09:10] <tjaalton> lool: I don't know
[09:13] <tjaalton> although I could file one
[09:19] <lool> tjaalton: Well they might not be aware of this if they still use libdrm's headers
[09:19] <tjaalton> they are aware, airlied is trying to persuade intel to get their act together
[09:29] <tjaalton> 2.6rc1 fails to build as well, using libdrm master
[09:34] <tjaalton> freedesktop bug 19132
[09:34] <tjaalton> same error as with 2.5.1
[09:36] <pwnguin> are we finally dispensing with control-alt-bksp?
[09:39] <pwnguin> cleverly hidden
[09:41] <tjaalton> yes
[09:44] <pwnguin> i gotta say, blueprints is confusing as hell
[09:59] <tjaalton> in general or this particular one
[10:10] <tseliot> tjaalton: is the new intel driver available now?
[10:10] <tseliot> the one with the fix to my problem
[10:10] <tjaalton> tseliot: it was a bug in the server
[10:10] <tjaalton> and it's available
[10:11] <tseliot> ok, thanks :-)
[10:14] <lool> tjaalton: thanks
[11:24] <tseliot> seb128: I gave mvo all the patches you need and he merged them. Now you can push gnome ;)
[11:25] <seb128> tseliot: ok thanks!
[11:50] <jcristau> lool: upstream knows about it, they'll probably fix up the kernel headers at some point. until then just build against libdrm?
[12:36] <tseliot> tjaalton: 3D effects (Compiz or Kwin) are very slow with the Intel driver now
[12:36] <tseliot> but hey, at least X starts now
[12:39] <tjaalton> tseliot: check the permissions on /dev/dri/card0
[12:41] <tseliot> tjaalton: crw-rw---- 1 root video 226
[12:41] <tjaalton> ..and if you're not on video-group -> fail
[12:42] <tjaalton> tseliot: btw, are you on linuxwacom-discuss?
[12:42] <tseliot> tjaalton: no, where is it?
[12:43] <tjaalton> the mailing list?
[12:43] <tseliot> tjaalton: aah, ok
[12:43] <tjaalton> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
[12:43] <tseliot> I'll post there soon
[12:44]  * tseliot > lunch
[12:44] <tjaalton> well, alexia death has looked into using dbus for hotplugging
[12:45] <tjaalton> and looks like it's possible to write a callout script which does things once you plug a tablet
[12:45] <tjaalton> +in
[12:50] <tjaalton> so, wacom hotplug should be around the corner, but there still are issues about where to store the config options etc.
[13:12] <lool> jcristau: Yup just what we're doing
[14:04] <tseliot> tjaalton: that would be interesting
[14:11] <tseliot> tjaalton: compositing is so slow that even KWin noticed and told me that it was better to disable it
[14:12] <tjaalton> tseliot: well, did you fix the permissions then?
[14:12] <tjaalton> you need to have rw-access to /dev/dri/card0
[14:12] <tseliot> tjaalton: I added myself to the video group
[14:13] <tjaalton> and logged out & in?
[14:13] <tseliot> tjaalton: I restarted Ubuntu
[14:13] <tjaalton> ok
[14:13] <tjaalton> dunno what's wrong then
[14:14] <tseliot> and I get direct rendering
[14:16] <tseliot> tjaalton: can you enable dbus in the xserver?
[14:23] <tjaalton> done in git
[14:27] <jcristau> tjaalton: it's called enable-config-dbus
[14:31] <tjaalton> jcristau: hah, so it is
[14:46] <tseliot> tjaalton: that will allow me wacom hotplug
[14:46] <tseliot> allow me to do
[14:47] <jcristau> you can't do wacom hotplug with config/hal?
[14:47] <tjaalton> jcristau: only one device (stylus/eraser/..)
[14:47] <tjaalton> to fully use wacom you need to set up at least three devices
[14:48] <jcristau> i thought NIDR was exported just for that reason?
[14:48] <tseliot> NIDR?
[14:48] <tjaalton> well I don't know what the details are
[14:48] <jcristau> tseliot: the function that creates a new input device
[14:48] <tjaalton> NewInputDeviceRequest
[14:49] <tseliot> jcristau: ok but does the wacom driver work with it?
[14:49] <tjaalton> http://sourceforge.net/mailarchive/forum.php?thread_name=200812162159.29671.alexiadeath%40gmail.com&forum_name=linuxwacom-discuss
[14:49] <jcristau> dunno. that's not the point though. if it doesn't, it can presumably be made to work
[14:50] <tseliot> tjaalton: I replied to her
[14:51] <tseliot> btw do you know why I get this is my Xorg.0.log? Failed to set tiling on front buffer rejected by the kernel
[14:52] <tseliot> it says the same about back and depth buffer
[14:53] <tjaalton> nope, no idea
[14:54] <tseliot> http://pastebin.com/m4606b1d9
[14:54] <tseliot> the full log ^^
[14:58] <tjaalton> upgrade your kernel
[14:58] <tjaalton> check dmesg for segfaults
[15:09] <tseliot> tjaalton: upgrade my kernel to which version?
[15:15] <tjaalton> to the latest one, yours is -2 while there is -3 available
[15:19] <tseliot> tjaalton: I can't see it in the repository
[15:20] <tjaalton> then change your mirror, preferably to just archive.u.c
[15:20] <tjaalton> gone ->
[15:22] <tseliot> found
[15:41] <tseliot> hmm, it doesn't seem to solve the problem
[15:48] <tjaalton> ok
[15:53] <tseliot> also I can't switch to vt without corrupting the screen
[15:54] <tjaalton> disable usplash
[16:09] <tseliot> right
[17:29] <bryce> superm1: erf, ATI is changing the bug escalation rules again
[17:30] <bryce> superm1: now they are no longer accepting new bugs once we've reached 5 (non-feature) EPR's
[17:42] <lool> Hi folks
[17:43] <crevette> salut lool
[17:43] <lool> On ATI R500 I had screen corruption all over the place until I forced EXA
[17:43] <lool> I'm using compiz
[17:43] <lool> Should we make EXA the new default for ati?
[17:48] <bryce> lool: yep
[17:48] <bryce> lool: in fact I've a blueprint open on doing exactly that... probably post-alpha2 I'll switch us over
[17:49] <bryce> I'd have done it already by now, but just been busy
[18:03] <lool> bryce: ok cool
[18:51] <bryce> tjaalton, tseliot, should bug #308410 get a mention on the alpha-2 release notes?
[19:19] <geeksquad> how do you restore the icons folder in /usr/share
[19:20] <geeksquad> hello
[19:21] <bryce> geeksquad: wrong channel.
[19:21] <geeksquad> whitch is the right channl
[19:22] <geeksquad> other than #ubuntu
[19:23] <geeksquad> bryce
[19:23] <bryce> dunno
[19:23] <bryce> this channel is only for X.org in ubuntu though.
[19:24] <geeksquad> oh maybe #gnome will work
[20:53] <tjaalton> bryce: just mention that blobs don't work. jockey doesn't offer them anymore
[20:55] <bryce> tjaalton: I think once alpha-2 is out, I'm going to pull a new -ati git snapshot and flip EXA on by default
[20:55] <bryce> *hopefully* that will be Friday
[20:55] <tjaalton> bryce: yeah
[21:00] <tjaalton> so, alexia tells me that she (?) managed to get wacom hotplug working using the dbus-script as a hal callout-script like debian-setup-keyboard is
[21:01] <tjaalton> the driver is a bit buggy so that some options are wrong, and of course no user settings are set, but that can be fixed while the device is plugged in
[21:02] <tseliot> yes, I talked to Alexia and I think we can work together
[21:04] <tseliot> bryce: do you know what can make my 965 slow when using 3D effects in Jaunty?
[21:05] <tseliot> bryce: log: http://pastebin.com/m4606b1d9
[21:21] <tseliot> videos have no tearing any more though
[21:24] <bryce> tseliot: mm, in your log I see some errors about tiling buffers rejected by the kernel
[21:25] <bryce> (WW) intel(0): Existing errors found in hardware state. <-- doesn't sound good either
[21:26] <bryce> however, I'm not familiar with these errors yet so don't know their significance
[21:26] <tseliot> ok
[22:19] <bryce> tjaalton: https://wiki.ubuntu.com/Hotkeys has a 'should be' diagram there now too.  let me know if there are any inaccuracies in it
[23:26] <tjaalton> bryce: nice pics, looks good so far :)
[23:26] <tjaalton> btw, now my laptop (965) refuses to start X properly :)
[23:27] <bryce> tjaalton: what did you run into?
[23:28] <bryce> I'm doing another ->intrepid upgrade on another 965 system (my laptop)
[23:28] <bryce> after alpha-2 I think I'm going to try a from-scratch reinstall
[23:28] <tjaalton> the display just goes blank, flashes a couple of times before that
[23:28] <tjaalton> maybe it didn't like me booting into xp to update my phone & remote
[23:30] <bryce> tjaalton: run intel_reg_dumper to collect the register settings while it's blank, then again when you get it working with vesa or a livecd or something, and send both to jesse
[23:31] <bryce> mm, could windows have left the gfx card registers in an inconsistent state for linux?
[23:31] <tjaalton> or just the fact that I have master snapshot of libdrm
[23:32] <bryce> tjaalton: btw I got confirmation that we are *not* doing KMS for jaunty.  That rumor we heard friday was apparently just a rumor
[23:33] <tjaalton> bryce: ok
[23:34] <tjaalton> yeah, downgrading libdrm helped