[07:41] is there some secret to finding the bylaws of The xorg foundation? [07:42] im trying to figure out whether that pledge drive for nouveau could have been handled by xorg foundation, but the lack of meeting minutes and bylaws is already suggesting "no" [07:42] oop, found em [09:43] hello there [09:43] hi [09:51] is this normal I can running compiz under intel graphic X3100 ? [09:51] "I can't" sorry [09:55] on intrepid? yes, currently [09:55] there is a patch for it, but the performance is pretty bad [09:56] okay [09:56] that's fine [09:56] there are a lot of changes on the intel graphics side in intrepid (sorry I don't follow closely developement) [09:56] ? [09:57] always :) [09:59] mesa 7.1 should have a bunch of changes for the DRI driver, and there's -intel 2.4.0 although it's not yet in intrepid [10:00] meh, I had hoped that the new mesa would have fixed the compiz issues [10:00] what issues? [10:01] the performance on intel are really poor, resizing a gtk windows lags a lot for me [10:01] this is really choppy [10:01] didn't you said earlier that you can not run it at all? [10:01] tjaalton: the fact that it would not run at all :) [10:02] mvo, just with metacity [10:02] mvo: it's fixed upstream, but the performance is not that good :) [10:02] perhaps I need to blame metacity [10:03] tjaalton: aha [10:03] since the "force greedy exa" patches haven't been forward ported [10:03] crevette: I'm still confused. so compiz does *not* run, but metacity does but that (== metacity) is slow? [10:03] * mvo nods [10:04] but seems like the driver only has 12MB of pixmap memory in its disposal, so that could be the reason [10:04] so it's trashing a lot [10:06] mvo, with metacity moving a windows is smooth, but resizing it is painfull slow [13:20] tjaalton, how come all of these bugs from releases earlier to intrepid are being assigned to fglrx-installer? fglrx-installer is intrepid only [13:29] superm1: because they aren't going to be fixed on lrm [13:30] tjaalton, a lot of what i'm seeing though doesn't even have logs and they are from much earlier releases [13:30] tjaalton, just mark them invalid, they're not going to be triaged if they're that old [13:30] superm1: feel free to close them :) [13:31] ok, will do in the future [13:31] so just skip the step of reassigning packages in those cases [13:31] thanks [13:31] i'd like to be able to track bugs that are fixable by packaging (there are a few here and there) [13:31] so extra bug mail at this stage doesn't help :) [13:32] yeah.. === mvo_ is now known as mvo____ === mvo____ is now known as mvo === mvo is now known as mvo____________ === mvo____________ is now known as mvo__ === mvo__ is now known as mvo [21:04] bryce: librecord probably will be enabled on debian too, now that there's actually a package that needs it [21:06] tjaalton: ah ok [21:08] tjaalton: btw I have a first cut for the console2fdi.sh script. dunno if it's correct, but nothing fancy [21:08] http://pastebin.ubuntu.com/32715/ [21:08] untested (obviously... already spotted a syntax error) [21:12] bryce: nice! btw, model should always be evdev, and it's already defined in 10-keymap.fdi [21:14] ok [21:18] I think I'll start an input hotplug page in the X wiki for keepign notes [21:18] XKBRULES is not defined in console-setup. base is set on 10-keymap.fdi, so that can be dropped as well [21:21] so we should only list it if it's set to something other than base? [21:21] or is it just always base? [21:21] always base [21:22] ah, so $XKBMODEL and $XKBRULES are always to be ignored? we only care about $XKBLAYOUT then? [21:22] and variant, options :) [21:23] why is rules always base? [21:23] the default layout is also defined on 10-keymap.fdi [21:24] oops [21:25] XkbRules is set in xorg.conf, but not sourced from /e/d/console-setup [21:25] and it's 'xorg' by default [21:25] hmm, sounds inconsistent [21:26] is that a bug or by design? [21:26] now if I only know the difference between those two [21:26] knew [21:26] beats me [21:26] does it change the fact that we should ignore it here? [21:27] not unless we change 10-keymap.fdi. so better just set it as 'xorg' [21:30] http://pastebin.ubuntu.com/32721/ [21:32] sample output: http://pastebin.ubuntu.com/32722/ [21:32] heh, looks simple [21:33] typo in capabilities :) [21:33] good catch [21:37] btw, do you have a non-us keyboard setup you could run this script on to doublecheck its output? [21:37] http://people.ubuntu.com/~bryce/InputHotplug/ [21:41] sure, a sec [21:42] yep, looks good [21:44] what about adding a notice that says "don't edit this file, edit /e/d/c-s instead and run .." [21:44] yeah [21:48] echo [21:48] echo '' [21:50] http://people.ubuntu.com/~bryce/InputHotplug/us-keyboard.fdi [21:52] sounds good