[00:19] <bryceh> can't wait :-)
[01:11] <BUGabundo> hi guys
[01:11] <BUGabundo> using nvidia with nouveua
[01:11] <BUGabundo> if I rotate my screen 90º, the touchpad doesn't rotate
[01:11] <BUGabundo> is this known, or should I file a bug for it?
[01:12] <bjsnider> nouveau
[01:12] <BUGabundo>  I never write it well
[01:12] <BUGabundo> sorry about that
[01:12] <bjsnider> show some respect for the glorious french language
[01:12] <BUGabundo> next time, choose something *easy* :p
[01:12] <mdeslaur> new? :)
[01:12] <bryceh> BUGabundo, yeah known issue
[01:12] <BUGabundo> thanks bryceh
[01:13] <BUGabundo> any bug I can sub to?
[01:13] <bryceh> BUGabundo, you can rotate it manually using xinput I think
[01:13] <bryceh> in fact I think there's a patch for it
[01:13] <BUGabundo> I made my laptop as a semi tablet, to read feeds :D
[01:14] <BUGabundo> ⎜   ↳ SynPS/2 Synaptics TouchPad              	id=12	[slave  pointer  (2)]
[01:14] <BUGabundo> I guess that's the one I want
[01:14] <bjsnider> mdeslaur, they could have called it "novus" which is latin for "new"
[01:14] <mdeslaur> bjsnider: yeah, but then I would have trouble remembering how to spell it :)
[01:14] <bryceh> I had a hell of a time trying to tell a native french speaker about the driver
[01:15] <bjsnider> a driver name has to have at least 2 syllables
[01:15] <BUGabundo> bryceh: LOLOLOL
[01:15] <bryceh> "Yes, use the nouveau driver."  "Oh, a new driver for nvidia?  What's it called?"
[01:15] <BUGabundo> new new 
[01:15] <BUGabundo> what ? new new 
[01:15] <bryceh> pretty much
[01:15] <BUGabundo> :DDD
[01:15] <mdeslaur> who's on first
[02:01] <Sarvatt> hmm, wonder why they never took that orientation patch upstream now now that you mention it
[02:05] <Sarvatt> ah waiting for XI2.1 https://bugs.freedesktop.org/show_bug.cgi?id=21129
[02:05] <ubot4> Freedesktop bug 21129 in Input/Core "General axis inversion and rotation support" [Normal,Assigned]
[02:05] <Sarvatt> (probably 2.2 now)
[02:08] <jewsucanuse> hey bryceh, i'm getting a weird x error.
[02:08] <jewsucanuse> after a few hours of use, most videos and images have color banding gradients
[02:08] <jewsucanuse> and this perists until an x restart.
[02:09] <Sarvatt> hmm its implemented for absolute devices http://cgit.freedesktop.org/xorg/xserver/commit/?id=6cccf0131c8464d8838cae2200730873d7dd9e45
[02:10] <Sarvatt> what driver?
[02:12] <Sarvatt> if its nvidia try changing away from the dynamic dithering mode? (shot in the dark)
[02:14] <jewsucanuse> i9515
[02:14] <jewsucanuse> *i915
[02:15] <jewsucanuse> natty bits btw
[02:16] <bryceh> jewsucanuse, no idea
[02:21] <LLStarks> i wish i could take a pic
[03:07] <bjsnider> libv, someone has created another via graphics driver -- "chrome" by name
[03:08] <bryceh> just what the world needs
[03:09] <bjsnider> at least via users have lots of choice
[03:09] <bjsnider> over 3000 possible drivers and counting
[03:09] <bjsnider> and none of them work!
[03:24] <Dr_Jakob> bjsnider: linky?
[03:26] <bjsnider> http://www.phoronix.com/scan.php?page=news_item&px=ODkzMQ
[11:06] <libv> bjsnider: one of the openchrome... let's say... people, did that
[11:07] <libv> bjsnider: commits are made to git by "root"
[11:08] <libv> of someone who has been, let's call it, "hanging around" graphics for the last 4-5 years, one would expect better, no?
[14:34] <soreau> Does anyone know if gallium will be default for radeon r3-5xx cards for natty?
[17:22] <ripps> I'm gonna try out Xorg-edgers on my rv350, see how gallium is coming along
[18:45] <ripps> hmmmm.... [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (1224704, 2, 4096, -12)
[18:46] <ripps> tried running pcsx to test opengl with a playstation game, now X seems to crash everytime I run a complex opengl program
[18:54] <ripps> cool, with r300g, I can force flash to use gpu acceleration
[19:06] <Sarvatt> we're going to get yelled at for maing this font default http://sarvatt.com/downloads/mono.png :)
[19:06] <Sarvatt> soreau: it already is, yeah
[19:08] <bjsnider> i think that font looks cool
[19:09] <ion> I’ll have to see it without the blurry font rendering to compare with the current DejaVu/Vera one.
[19:11] <vish> Sarvatt: reboot after updates! ;) 
[19:14] <Sarvatt> ion: without the blurry font rendering? it looks screwed up at anything but subpixel smoothing/slight hinting at the moment
[19:16] <Sarvatt> http://sarvatt.com/downloads/mono-subpixel-full.png
[19:16] <ripps> awesome, 3d css transforms work in chromium now. and they look awesome
[19:16] <ion> If a horizontal or vertical line has subpixels that are anywhere between the background color and the text color, the rendering is using lower frequency content than would be possible, i.e. blur. That might look aesthetically nice, but nobody can claim it’s not less readable. We’ve drawn our characters with sharp lines through the human history for a reason.
[19:17] <ion> Even the -full one is blurry: alas, you need to do sudo perl -i -pwe 's/\000\Klcddefault\000/lcdlegacy\000\000/g' /usr/lib/gnome-settings-daemon-2.0/libxsettings.so to get sharp fonts in Ubuntu Gnome.
[19:18] <ion> The powers that be haven’t provided us with a better way to do it, and i haven’t got around to creating a good patch. :-)
[19:19] <bjsnider> i don't see the blur in that screenshot
[19:20] <ion> It would be obvious if you’d see the really sharp text next to it. You could fire up xmag and look at any horizontal or vertical line to see the between-0%-and-100% subpixels.
[19:20] <bjsnider> xmag?
[19:21] <ion> Alt-F2, xmag, Enter
[19:22]  * bjsnider nods
[19:22] <ion> The solution to get aesthetically good-looking fonts is getting displays with considerably better resolutions, not using blurry rendering to approximate it with the cost of readability.
[19:22] <bjsnider> my monitor only does 96 dpi
[19:23] <ion> ditto
[19:23] <ion> Still waiting for the 300 DPI displays. :-P
[19:24] <ion> …affordable ones, that is.
[19:27] <bjsnider> why stop at 300?
[19:27] <bjsnider> we can't even really get much past 96 at this point though
[19:28] <ion> I didn’t mean the progress should stop at 300. :-)
[19:30] <ilmari> my home laptop is 140dpi, my work one is 147
[19:30]  * mdeslaur will run his 300 DPI display at 96 DPI to get massive resolution :P
[19:30] <ilmari> 1440x900 on 12.1" and 1920x1200 on 15.4", respectively
[19:31] <bjsnider> at 300 dpi the windows icons would be so small that they'd be invisible
[19:31] <ion> mdeslaur: That makes no sense. In LCDs, the resolution is a physical property of the display that doesn’t change. :-)
[19:32] <Sarvatt> vish: why'd you make me reboot, gnome classic session breaks in new interesting ways every friday update :)
[19:32] <mdeslaur> ion: right, I meant massive window real estate :P
[19:32] <vish> oops!
[19:33] <ion> bjsnider: Toolkits should scale images (picking the closest appropriate bitmap version available for small sizes) based e.g. font size.
[19:34] <ion> mdeslaur: You mean you want small fonts? Then the setting you’re after is the font size. :-)
[19:34] <bjsnider> ion, windows doesn't
[19:34] <ilmari> bjsnider: and?
[19:35] <ion> bjsnider: Yes, i said “decent”. ;-) Anyway, as high-resolution displays become available, i’m sure Bill will have to follow.
[19:35] <bjsnider> actually maybe windows 7 does, i dealt with a guy who had a laptop with a large resolution and small display and his icons were tiny
[19:35] <bjsnider> but he was using vista
[19:35] <mdeslaur> ion: okok, you win :P
[19:35] <Sarvatt> ion: http://sarvatt.com/downloads/mono-full-lcddefault.png
[19:35] <ilmari> icons should be vector graphics anyway
[19:35] <Sarvatt> whoops lcdlegacy I meant
[19:36] <ion> sarvatt: Not bad. I can see further hinting is needed, but i could get used to that.
[19:36] <ion> Thanks for the screenshot. :-)
[19:37] <ion> By switching between http://sarvatt.com/downloads/mono-full-lcddefault.png and http://sarvatt.com/downloads/mono-subpixel-full.png one can clearly see the difference in blurriness.
[19:37] <ion> Not to mention between http://sarvatt.com/downloads/mono.png and http://sarvatt.com/downloads/mono-full-lcddefault.png
[19:38] <bjsnider> Sarvatt, does the led on your wifi chip work?
[19:40] <mdeslaur> ugh, I hate full hinting
[19:45] <Sarvatt> bjsnider: atk9k is all kinds of screwed up in the latest kernels but yeah the led works fine
[20:08] <Sarvatt> bjsnider: knew it was too good to be true that we could keep the same basic packaging between 3 releases for nvidia/fglrx :)
[20:08] <Sarvatt> (see end of https://lists.ubuntu.com/archives/natty-changes/2010-December/date.html )
[20:09] <bjsnider> well, dumping the modalias package is fine by me
[20:10] <bjsnider> i wonder if it's possible to move all of nvidia-common into jockey and then just have jockey and the drivers
[20:11] <bjsnider> of course that's not the way debian does things, they have to have separate packages for every little thing
[20:15] <Sarvatt> hmm guess we could build lib32vdpau in the PPA so people can get flash acceleration on amd64, I'm totally stumped on what to do with it in the archive though
[21:56] <soreau> Sarvatt: Awesome, thanks.