[01:27] <EagleScreen> hello
[01:27] <EagleScreen> hello
[01:28] <EagleScreen> will be available soon intel driver 2.15.0 in X Updates PPA?
[03:09] <jcastro> bryceh: ping me next week if you want me to slide that X session out of monday
[03:15] <bryceh> jcastro, yeah we'd like it to be thurs or friday
[03:16] <jcastro> the scheduler will run again tomorrow
[03:16] <jcastro> but remind me next week after the schedule's settled down
[03:17] <bryceh> jcastro, sounds like you need a todo list program ;-)
[03:18] <jcastro> bryceh: this is my "if they care they will ping again but I won't make too much of an effort right now but I want to sound useful."
[03:19] <bryceh> *snortle*
[18:44] <bjsnider> ricotz, the default gnome 3 font doesn't seem to be available here. is it on your system?
[18:45] <bjsnider> cantarell
[18:47] <ricotz> bjsnider, no it isnt available, i just customized them
[19:21] <EagleScreen> bryceh: can I expect an upload of intel driver 2.15.0 soon in X-Updates PPA??
[19:21] <EagleScreen> anyone else?
[19:35] <bryceh> EagleScreen, perhaps, if someone has some freetime to do it, although with the release people are pretty busy
[19:35] <bryceh> EagleScreen, would you be interested in joining the xorg-edgers team to help do updates?
[19:36] <EagleScreen> i am a beginer packager
[19:38] <EagleScreen> but if you think I can help.. i'd join
[19:39] <bryceh> EagleScreen, that's probably fine - there are scripts you run to generate the packages, so it doesn't require a heavy amount of packaging know-how (except when you need to troubleshoot problems, which others can help with anyway)
[19:39] <bryceh> let me dig up some additional info for you to look at 
[19:41] <bryceh> EagleScreen, on https://launchpad.net/~xorg-edgers scroll down to "Contributors to xorg-edgers be welcome" and read that section
[19:42] <bryceh> it shows where you can get the script, and how to run it to get a new upstream snapshot of a video driver
[19:42] <bryceh> EagleScreen, give that a try and see if you can make a 2.15.0 snapshot driver for yourself
[19:47] <EagleScreen> ok
[19:48] <EagleScreen> but i was thinking in make stable 2.15.0 not a git snapshot
[19:50] <EagleScreen> i was playing with debian unstable (KDE) and i have seen that desktop effects works pretty well with my intel card, then i thougth it was by the 2.15.0 driver newer than 2.14 in Kubuntu natty, but now i see that debian esting with 2.14.0 also have good desktop effects
[19:51] <EagleScreen> in natty ther are very slow and KDE disable them
[19:52] <EagleScreen> so it must be another thing more than the 2.15.0
[20:04] <bryceh> EagleScreen, ok well one of us will eventually get 2.15.0 into x-updates once some of the more pressing issues are taken care of
[20:05] <bryceh> actually with the release out now it's probably a good time to refresh x-updates.
[20:06] <EagleScreen> yes, but 2.15.0 may not fix the desktop effects issue since they work in Debian under 2.14.0
[20:06] <EagleScreen> the difference must be in another X package, may be some library
[20:07] <Sarvatt> it's not in there yet because of libdrm, the nvidia package will depend on the newer libdrm (even though it doesn't use it) and a lot of people just install the nvidia deb from that PPA which will screw up things
[20:07] <Sarvatt> kde effects being slow would be mesa
[20:08] <bryceh> heya Sarvatt
[20:08] <Sarvatt> more than likely I bet you're seeing that blur is disabled automatically in debian, but its getting enabled in ubuntu which is leading to the disable effects fallback
[20:09] <Sarvatt> heyo bryceh!
[20:09] <EagleScreen> both natty and Debian have 7.10.2
[20:10] <Sarvatt> yeah but debian does not revert the commit that breaks direct rendering in KDE in their mesa
[20:10] <Sarvatt> (which means no blur automatically on intel)
[20:12] <EagleScreen> then, direct rendering is broken now in Debian testing? how do I check it?
[20:13] <Sarvatt> i'm not familiar with KDE to answer that, I think there's a lot that tells you if direct rendering is enabled? let me dig up the bug reports
[20:13] <Sarvatt> log rather
[20:14] <Sarvatt> EagleScreen: ~/.xsession-errors
[20:14] <Sarvatt> on debian it will say
[20:14] <bjsnider> ricotz, the problem ryan paul complained about in his review of gnome 3, where there's too much white space everywhere is due to the cantarell font. i just installed and tested it. the ubuntu font looks better from the standpoint of whitespace.
[20:14] <Sarvatt> Direct rendering:                       no
[20:14] <Sarvatt> Requires strict binding:                yes
[20:14] <Sarvatt> GLSL shaders:                           no
[20:14] <Sarvatt> and on natty it will say
[20:14] <Sarvatt> Direct rendering:                       yes
[20:14] <Sarvatt> Requires strict binding:                yes
[20:14] <Sarvatt> GLSL shaders:                           yes
[20:15] <bjsnider> looks like cantarell adds a lot of padding on the top of the letters
[20:17] <EagleScreen> i dont see that lines in the file
[20:17] <Sarvatt> EagleScreen: run kwin manually maybe? should be in the terminal output when you run it
[20:21] <Sarvatt> alternatively, just disable blur and lanczos in kwin to stop the fallbacks
[20:21] <EagleScreen> i still dont see it, neither on terminal
[20:21] <EagleScreen> i dont know what blur is
[20:21] <EagleScreen> and how to disable it
[20:23] <Sarvatt> I dont know how to disable it in KDE either, was under the impression there was an option in the GUI to do it though. anyone else here know?
[22:33] <Sarvatt> quite a lot of interesting linaro sessions this time around