/srv/irclogs.ubuntu.com/2009/03/27/#ubuntu-x.txt

tjaaltonoh cool, looks like the fedora patches made it in wacom-tools 0.8.3.104:50
superm1bryce, tjaalton i've got a fix backported from mesa git that fixes that mythtv bug.  y'all cool with me uploading it?07:48
tjaaltonsuperm1: is it included in 7.4?08:05
superm1tjaalton, i don't think it is 08:05
tjaaltonwhich commit?08:05
superm1529d1d720e1422bad1880ef33fae1c9423112d2e08:05
superm1i didn't see it in the 7.4 branch browsing the webif08:05
tjaaltonhmh, 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 that08:06
superm1    the server's not allowing mismatched fbconfigs.08:06
tjaaltonok, found it08:07
superm1is it in 7.4, or you found it in trunk?08:08
tjaaltonnot in 7.4, but I'll add it while merging08:08
superm1okay for now, i'm going to do an upload with it so i can get re-rolled disks tomorrow hopefully08:08
tjaaltonok08:08
tjaaltontoss me the diff so I can add it to git..08:09
superm1http://pastebin.com/f1ae8547a08:09
tjaaltonthanks08:12
tjaaltonyou should probably get an account on alioth :)08:12
tjaalton(.debian.org)08:12
superm1yeah i should.  08:12
superm1where do i fill out such requests?08:13
tjaaltonthere's a webform08:13
superm1tjaalton,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 days08:13
tjaaltonsuperm1: probably late for 7.4, but 7.4.1 should follow at some point08:14
tjaaltonbut maybe ask brian paul08:14
superm1is he on IRC?08:14
tjaaltonat least not atm08:15
tjaaltonbut mesa3d-dev@lists.sf.net should be ok08:15
superm1okay i'll fire an email that way.  i hope they dont make me subscribe to send08:16
tjaaltonhis email is brianp at vmware.com08:16
tjaaltonif the list is hostile :)08:16
tjaaltonbryce: I can push the changes to xorg-server git so you can stop worrying about it and start with a clean branch?08:19
brycethanks08:19
superm1hm alioth makes me take username-guest?08:19
superm1i can't just register username?08:19
tjaaltonsuperm1: yes, non-dd's08:19
bryceno08:19
superm1that's a bit annoying08:20
bryceit's only the start08:20
tjaaltona bit, but not too much.. you don't need to know about it other than when cloning08:21
superm1okay so now i dont see anywhere obvious to add an ssh key for git access then?08:21
tjaaltonyou need to be added to the pkg-xorg team08:22
tjaaltonoh, the keys are behind account maintenance08:23
brycenight, heading to bed.  cya.08:24
superm1i 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 then08:24
tjaaltonnight bryce08:24
tjaaltondon't get the git bugs bite.. :P08:25
superm1okay i requested access. i guess jcristau will have to ack that then08:26
tjaaltonyep08:26
superm1i'm headed to bed too. night y'all08:26
tjaaltonbye08:26
jcristausuperm1: added.08:48
dholbachsince a few days my brother's metacity is using 100% CPU in jaunty - could this be an X issue?09:26
dholbachseb128 says metacity didn't change in the last 1.5 months09:26
dholbachit09:26
dholbachit's a  Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller  card in his laptop09:26
dholbachhe doesn't use compositing09:27
tjaaltondholbach: dunno, my bet is that metacity is just confused09:35
dholbachtjaalton: about what? :)09:40
jcristauwhat's it doing?09:41
tjaaltondholbach: about it's state.. maybe cleaning the configs might help09:47
dholbachtjaalton: which do you suggest?09:48
tjaaltondholbach: it's been a while since I used it, so don't know how to clear it09:50
tjaaltonat least there's ~/.metacity09:50
dholbachI'll ask him to try09:54
RAOFBuild, 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:27
Ngdoes tormod lurk around these parts?10:52
tjaaltonsometimes, yes10:54
NgI'm just curious about how I can match up his -intel git snapshot changelog with what upstream call things.10:55
Nghe says it includes up to commit 69c84f2c8204771b68f40ed64e64657237b54546 and upstream wanted me to try 2.6.99.90210:56
* Ng tsks at cgit for not making it easier to see a log of these hashes10:56
Ngwhat'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:56
tjaaltongitweb was easier in that regard10:57
Ngaha, that's the second-to-most-recent commit on master. win.10:57
tjaaltonoh, master10:57
tjaaltonso not on 2.7 branch10:57
Nghttp://launchpadlibrarian.net/24376936/xserver-xorg-video-intel_2.6.99.1%2Bgit20090327.69c84f2c-0ubuntu0tormod_source.changes10:59
Ngsuggests it's master10:59
Ngbut I have approximately 0 familiarity with the way this stuff is structured for intel11:00
tjaaltonsame as elsewhere.. the release branches are for bugfixes, master for development11:00
tjaaltonbryce: to not need -f when using git add is to use .diff postfix :)14:32
tjaaltondon't know why .gitignore has *.patch on it14:33
tjaaltonxorg-server git updated14:34
tjaaltonmesa 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:34
tjaaltondamn, gotta run.. get to sing Händel today, again :P14:35
jcristautjaalton: i guess because git format-patch produces *.patch and it makes sense for upstream to ignore that14:43
tormoddid we get some DPI policy changes lately?19:32
brycetormod: apparently...  I'm looking for the bug report19:32
tormodI had these big fat fonts for a while, now it's back to tiny19:32
brycehttps://wiki.ubuntu.com/JauntyJackalope/TechnicalOverview?action=diff&rev2=67&rev1=6619:32
bryceaccording to slangasek the dpi thing has been reverted by asac19:33
brycewhich is sort of a bummer to me, but at least this time it's not being blamed on X iniquities ;-)19:33
tormodthis was not discussed anywhere, like on ubuntu-x ?19:33
bryceI guess not; bug 349140 was the first I got light of it19:34
ubottuLaunchpad bug 349140 in xserver-xorg-video-intel "invalid lcd dpi calculated" [Undecided,New] https://launchpad.net/bugs/34914019:34
bryce#345189 seems to be the bug attached to the change... looking...19:34
brycechanged in libgnome19:35
bryce  * debian/libgnome2-common.gconf-defaults: fix LP: #345189 - regression after19:35
bryce    switching system font size to 13.333; we backout the new font defaults made in19: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 +010019:35
tormodwhere is 96 dpi forced?19:37
tormodit is not on the X server command line AFAICS19:37
bryceno, it's forced in libgnome19:37
brycetormod: it's telling that kubuntu has not been forcing the dpi for some time, and trusts what X provides19:38
tormodso no-gnome applications will get the correct DPI from X then19:38
tormodshouldn't they rather fix Gnome?19:39
brycehistorically 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 forced19:39
brycetormod: fixing Gnome seems the sensible solution to me as well19:39
brycetormod: maybe it's too hard for them though *shrug*19:40
brycee.g. it may require individually fixing a lot of different apps, or altering font definitions or something19:40
bryceat 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 up19:41
tormodyes this kind of hides bugs instead of getting them fixed19:41
bryceI 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:41
tormodwe got a bunch of edid quirking working thanks to the KDE reports19:42
tormodI liked having an A4 paper on the screen being the size of an A4 paper etc19:43
* bryce nods19:43
tormodI hope they drop the dpi-forcing ASAP in Karmic19:44
* bryce waves a wand and turns 349140 into a libgnome bug19:44
bryceactually 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:44
brycetormod: mm, in 345189 it appears asac is working on fixing each application individually.. that's why there's so many bug tasks there19:46
brycesounds like the root issue is application developers confusing "pixel-size fonts" with "point-size fonts"19:47
tormodgood to hear he is working on it19:47
tormodmesa seems to need plenty of fixes, are we gonna get 7.4 in?19:50
brycetormod: timo's working on it19:55
tormodtjaalton: you may want to cherry-pick for bug 32485420:02
ubottuLaunchpad bug 324854 in xserver-xorg-video-intel "DRI2: (UXA) white transparency artifacts with compiz [patch]" [Undecided,Invalid] https://launchpad.net/bugs/32485420:02

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!