[04:51] <tjaalton> bryce: yes, I think at some point that needs to be done
[04:52] <tjaalton> currently it just affects new installations
[04:52] <tjaalton> but we have more pending changes to come :) (discover, input-hotplug..)
[05:20] <bryce> yeah
[06:41] <ubotu> New bug: #177609 in xorg-server (main) "nvidia-glx won't upgrade" [Undecided,New] https://launchpad.net/bugs/177609
[07:25] <ubotu> New bug: #177614 in xorg (main) "[Feisty,Gutsy] Switching to tty yields black screen (SiliconMotion)" [Undecided,New] https://launchpad.net/bugs/177614
[08:22] <superm1> hey bryce 
[08:22] <bryce> heya
[08:22] <superm1> could you look briefly to see if you agree this bug is classified in the right area: https://bugs.edge.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/104613 ?
[08:22] <ubotu> Launchpad bug 104613 in linux-restricted-modules-2.6.24 "restricted-manager does not correctly enable XvMC with nVidia binary graphics drivers" [Undecided,New] 
[08:23] <superm1> i wasn't sure if it should really be handled in l-r-m
[08:23] <superm1> or if it makes more sense in restricted-manager
[08:23] <bryce> hmm
[08:24] <superm1> i just revived it a few minutes ago since there has been a lot of confusion surrounding it from #ubuntu-mythtv and on the forums
[08:24] <bryce> restricted-manager might be a better choice for it
[08:25] <bryce> I guess it depends on whether it's lrm or restricted-manager that does the xvmc setting
[08:26] <superm1> well if it was in lrm, then people installing from just nvidia-glx or nvidia-glx-new would benefit too
[08:26] <bryce> in any case, I suspect it'll get faster attention from r-m, and if it's determined to really belong to l-r-m, they can bounce it there later
[08:26] <superm1> but then again restricted manager usually handles these configurationy things
[08:26] <superm1> similar to how xorg.conf is typically modified to turn off things like the nvidia splash screen
[08:27]  * bryce nods
[08:27] <superm1> okay i'll reclass it to restricted-manager again then.  thanks :)
[08:28] <bryce> cool, sure :-)
[08:28] <superm1> i was going to let you know as well, there was some discussion on beta mailing list.  the amd driver might be getting support to automatically install drivers from the .run file
[08:28] <tjaalton> well, nvidia* is uninstallable on hardy right now :)
[08:28] <superm1> so that work that tseliot is doing with envyng might not be all that necessary for them 
[08:28] <superm1> by autoinstall i'm meaning nicely with the package manager 
[08:28] <superm1> and such
[08:32] <bryce> it'll be interesting to see how that turns out
[08:32] <superm1> yeah, i've been reluctant to join your guys' discussion so as to not trump it since this stuff isn't final
[13:40] <ubotu> New bug: #158215 in xserver-xorg-video-nv (main) "Screen does not display properly after boot up\" [Undecided,New] https://launchpad.net/bugs/158215
[14:00] <ubotu> New bug: #177658 in xserver-xorg-video-ati (main) "[hardy] Blank GDM screen with ATI R420 [X800XT PE]" [Undecided,New] https://launchpad.net/bugs/177658
[14:16] <ubotu> New bug: #158109 in xserver-xorg-video-nv (main) "For Hardy: enabling desktop effects with NVidia card on LiveCD is impossible" [Undecided,New] https://launchpad.net/bugs/158109
[14:31] <ubotu> New bug: #176888 in xserver-xorg-video-intel (universe) "xbacklight not working in hardy, intel GM965" [Undecided,New] https://launchpad.net/bugs/176888
[15:01] <ubotu> New bug: #144277 in xorg (main) "Mouse latency (sweep-selection precision) in Ubuntu" [Undecided,New] https://launchpad.net/bugs/144277
[15:35] <ubotu> New bug: #177680 in xorg (main) "leaking pixmaps" [Undecided,New] https://launchpad.net/bugs/177680
[15:59] <ubotu> New bug: #155366 in xserver-xorg-driver-nv (main) "Rendering of transparent backgrounds broken" [Undecided,New] https://launchpad.net/bugs/155366
[16:04] <ubotu> New bug: #148138 in xserver-xorg-driver-ati (main) "High cpu usage on Xorg with gnome-terminal and transparency" [Undecided,New] https://launchpad.net/bugs/148138
[16:06] <ubotu> New bug: #159238 in gnome-terminal (main) "Garbage in gnome-terminal (dup-of: 120858)" [Undecided,Invalid] https://launchpad.net/bugs/159238
[17:02] <ubotu> New bug: #139313 in xorg (main) "nvidia dual head twinview (pseudo-xinerama): gnome-panel and maximized windows span both heads on first login" [Undecided,Confirmed] https://launchpad.net/bugs/139313
[22:49] <superm1> bryce, i've gotten word that catalyst 7.12 was publicly announced.  it should be sane for inclusion in hardy as firegl hardware is again officially supported.
[22:49] <bryce> ah good to know
[22:50] <superm1> it has its quirks (as i've reported and they are listed on the known issues), but it is a good improvement
[23:06] <ScislaC> superm1: do they have aiglx working with the new xorg yet?
[23:06] <superm1> it should be on non firegl hardware
[23:07] <ScislaC> (from everything I've seen Catalyst 7.11 &  FGLRX 8.42 don't work with hardy's version)
[23:07] <ScislaC> and that was also my personal experience
[23:08] <ScislaC> superm1: do you have a link to the known issues?
[23:08] <ScislaC> I'm curious if the new one will also peg one of the cores on my dual core as well
[23:09] <ScislaC> superm1: reading on Phoronix :)
[23:13] <ScislaC> bryce: evil bug... "Connecting a display device that supports 1680x1050 to a system running Linux may result in a maximum display resolution of 1280x1024 only being available"  Does AMD specifically target all of my hardware to find a way to make it a pain? ;)
[23:15] <superm1> haha