[04:50] <tjaalton> oh cool, looks like the fedora patches made it in wacom-tools 0.8.3.1
[07:48] <superm1> bryce, tjaalton i've got a fix backported from mesa git that fixes that mythtv bug.  y'all cool with me uploading it?
[08:05] <tjaalton> superm1: is it included in 7.4?
[08:05] <superm1> tjaalton, i don't think it is 
[08:05] <tjaalton> which commit?
[08:05] <superm1> 529d1d720e1422bad1880ef33fae1c9423112d2e
[08:05] <superm1> i didn't see it in the 7.4 branch browsing the webif
[08:06] <tjaalton> hmh, the search doesn't find it.. what's the commit msg?
[08:06] <superm1>     This lets swrast produce an fbconfig suitable for the root visual now that
[08:06] <superm1>     the server's not allowing mismatched fbconfigs.
[08:07] <tjaalton> ok, found it
[08:08] <superm1> is it in 7.4, or you found it in trunk?
[08:08] <tjaalton> not in 7.4, but I'll add it while merging
[08:08] <superm1> okay for now, i'm going to do an upload with it so i can get re-rolled disks tomorrow hopefully
[08:08] <tjaalton> ok
[08:09] <tjaalton> toss me the diff so I can add it to git..
[08:09] <superm1> http://pastebin.com/f1ae8547a
[08:12] <tjaalton> thanks
[08:12] <tjaalton> you should probably get an account on alioth :)
[08:12] <tjaalton> (.debian.org)
[08:12] <superm1> yeah i should.  
[08:13] <superm1> where do i fill out such requests?
[08:13] <tjaalton> there's a webform
[08:13] <superm1> tjaalton,also do you know the right people to ask to pull that into 7.4?  i suspect other distros that will be picking up xorg server 1.6 will want to get that too without having to go on the manhunt i did the last few days
[08:14] <tjaalton> superm1: probably late for 7.4, but 7.4.1 should follow at some point
[08:14] <tjaalton> but maybe ask brian paul
[08:14] <superm1> is he on IRC?
[08:15] <tjaalton> at least not atm
[08:15] <tjaalton> but mesa3d-dev@lists.sf.net should be ok
[08:16] <superm1> okay i'll fire an email that way.  i hope they dont make me subscribe to send
[08:16] <tjaalton> his email is brianp at vmware.com
[08:16] <tjaalton> if the list is hostile :)
[08:19] <tjaalton> bryce: I can push the changes to xorg-server git so you can stop worrying about it and start with a clean branch?
[08:19] <bryce> thanks
[08:19] <superm1> hm alioth makes me take username-guest?
[08:19] <superm1> i can't just register username?
[08:19] <tjaalton> superm1: yes, non-dd's
[08:19] <bryce> no
[08:20] <superm1> that's a bit annoying
[08:20] <bryce> it's only the start
[08:21] <tjaalton> a bit, but not too much.. you don't need to know about it other than when cloning
[08:21] <superm1> okay so now i dont see anywhere obvious to add an ssh key for git access then?
[08:22] <tjaalton> you need to be added to the pkg-xorg team
[08:23] <tjaalton> oh, the keys are behind account maintenance
[08:24] <bryce> night, heading to bed.  cya.
[08:24] <superm1> i guess i need to be on a team for it to be exposed in the UI.  how lets see if i can find where to request access to a team then
[08:24] <tjaalton> night bryce
[08:25] <tjaalton> don't get the git bugs bite.. :P
[08:26] <superm1> okay i requested access. i guess jcristau will have to ack that then
[08:26] <tjaalton> yep
[08:26] <superm1> i'm headed to bed too. night y'all
[08:26] <tjaalton> bye
[08:48] <jcristau> superm1: added.
[09:26] <dholbach> since a few days my brother's metacity is using 100% CPU in jaunty - could this be an X issue?
[09:26] <dholbach> seb128 says metacity didn't change in the last 1.5 months
[09:26] <dholbach> it
[09:26] <dholbach> it's a  Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller  card in his laptop
[09:27] <dholbach> he doesn't use compositing
[09:35] <tjaalton> dholbach: dunno, my bet is that metacity is just confused
[09:40] <dholbach> tjaalton: about what? :)
[09:41] <jcristau> what's it doing?
[09:47] <tjaalton> dholbach: about it's state.. maybe cleaning the configs might help
[09:48] <dholbach> tjaalton: which do you suggest?
[09:50] <tjaalton> dholbach: it's been a while since I used it, so don't know how to clear it
[09:50] <tjaalton> at least there's ~/.metacity
[09:54] <dholbach> I'll ask him to try
[10:27] <RAOF> Build, you darn git-buildpackage.  I know I'm not on master!  I'm on ubuntu-jaunty because I'm building a package for Jaunty, damnit!
[10:52] <Ng> does tormod lurk around these parts?
[10:54] <tjaalton> sometimes, yes
[10:55] <Ng> I'm just curious about how I can match up his -intel git snapshot changelog with what upstream call things.
[10:56] <Ng> he says it includes up to commit 69c84f2c8204771b68f40ed64e64657237b54546 and upstream wanted me to try 2.6.99.902
[10:56]  * Ng tsks at cgit for not making it easier to see a log of these hashes
[10:56] <Ng> what's the point of having a globally unique identifier for each commit if you're not going to make that the easiest way to track history?! ;)
[10:57] <tjaalton> gitweb was easier in that regard
[10:57] <Ng> aha, that's the second-to-most-recent commit on master. win.
[10:57] <tjaalton> oh, master
[10:57] <tjaalton> so not on 2.7 branch
[10:59] <Ng> http://launchpadlibrarian.net/24376936/xserver-xorg-video-intel_2.6.99.1%2Bgit20090327.69c84f2c-0ubuntu0tormod_source.changes
[10:59] <Ng> suggests it's master
[11:00] <Ng> but I have approximately 0 familiarity with the way this stuff is structured for intel
[11:00] <tjaalton> same as elsewhere.. the release branches are for bugfixes, master for development
[14:32] <tjaalton> bryce: to not need -f when using git add is to use .diff postfix :)
[14:33] <tjaalton> don't know why .gitignore has *.patch on it
[14:34] <tjaalton> xorg-server git updated
[14:34] <tjaalton> mesa merged in my local ubuntu-next branch.. I'm wondering if we could push that and use for stuff like this (not knowing if 7.4 will be accepted or not, but allowing working on it together)
[14:35] <tjaalton> damn, gotta run.. get to sing Händel today, again :P
[14:43] <jcristau> tjaalton: i guess because git format-patch produces *.patch and it makes sense for upstream to ignore that
[19:32] <tormod> did we get some DPI policy changes lately?
[19:32] <bryce> tormod: apparently...  I'm looking for the bug report
[19:32] <tormod> I had these big fat fonts for a while, now it's back to tiny
[19:32] <bryce> https://wiki.ubuntu.com/JauntyJackalope/TechnicalOverview?action=diff&rev2=67&rev1=66
[19:33] <bryce> according to slangasek the dpi thing has been reverted by asac
[19:33] <bryce> which is sort of a bummer to me, but at least this time it's not being blamed on X iniquities ;-)
[19:33] <tormod> this was not discussed anywhere, like on ubuntu-x ?
[19:34] <bryce> I guess not; bug 349140 was the first I got light of it
[19:34] <bryce> #345189 seems to be the bug attached to the change... looking...
[19:35] <bryce> changed in libgnome
[19:35] <bryce>   * debian/libgnome2-common.gconf-defaults: fix LP: #345189 - regression after
[19:35] <bryce>     switching system font size to 13.333; we backout the new font defaults made in
[19:35] <bryce>     2.25.1-0ubuntu2 and force 96 dpi again (see 2.24.1-1ubuntu3)
[19:35] <bryce>  -- Alexander Sack <asac@ubuntu.com>  Mon, 23 Mar 2009 12:34:41 +0100
[19:37] <tormod> where is 96 dpi forced?
[19:37] <tormod> it is not on the X server command line AFAICS
[19:37] <bryce> no, it's forced in libgnome
[19:38] <bryce> tormod: it's telling that kubuntu has not been forcing the dpi for some time, and trusts what X provides
[19:38] <tormod> so no-gnome applications will get the correct DPI from X then
[19:39] <tormod> shouldn't they rather fix Gnome?
[19:39] <bryce> historically we've typically gotten the bug reports about monitors with invalid physical dimension EDID only from KDE users, since that messes up the dpi X reports.  GNOME users don't see those kinds of bugs since it's been forced
[19:39] <bryce> tormod: fixing Gnome seems the sensible solution to me as well
[19:40] <bryce> tormod: maybe it's too hard for them though *shrug*
[19:40] <bryce> e.g. it may require individually fixing a lot of different apps, or altering font definitions or something
[19:41] <bryce> at least it would be nice if they implemented as an option, so testers could switch the 96 dpi forcing off, so they can work on getting the apps fixed up
[19:41] <tormod> yes this kind of hides bugs instead of getting them fixed
[19:41] <bryce> I anticipate we're going to see a bunch of bug reports against X.org now, that say "Hey, you guys finally got my font dpi right in Jaunty, but now with the release it's regressed to 96 again...??"
[19:42] <tormod> we got a bunch of edid quirking working thanks to the KDE reports
[19:43] <tormod> I liked having an A4 paper on the screen being the size of an A4 paper etc
[19:43]  * bryce nods
[19:44] <tormod> I hope they drop the dpi-forcing ASAP in Karmic
[19:44]  * bryce waves a wand and turns 349140 into a libgnome bug
[19:44] <bryce> actually it'll be nice for a change to be able to forward a bunch of X bugs to gnome, instead of the other way round ;-)
[19:46] <bryce> tormod: mm, in 345189 it appears asac is working on fixing each application individually.. that's why there's so many bug tasks there
[19:47] <bryce> sounds like the root issue is application developers confusing "pixel-size fonts" with "point-size fonts"
[19:47] <tormod> good to hear he is working on it
[19:50] <tormod> mesa seems to need plenty of fixes, are we gonna get 7.4 in?
[19:55] <bryce> tormod: timo's working on it
[20:02] <tormod> tjaalton: you may want to cherry-pick for bug 324854