Look: software evolves, and sometimes API breaks and things like that are necessary. While you may be unhappy about the situation, there is indeed nothing the open community can do if the developers behind the closed source drivers do not want to react on the issue. That is, if they really do not want to, maybe the issue has simply not been brought to their attention. So, please, if you care about this issue being fixed as we all do here, why do you not take the step and try to obtain at least some sort of feedback from their developers by posting the problem there - i.e. for the nvidia driver to start with? I'd to it myself but I have no nvidia card atm to provide specific information if they require it, and really, it is not such a big deal to send them a few words.
On 04/20/2010 01:08 PM, Dan Burke wrote: > This was not brought up at nvnews because it was not originally a Binary > Blob issue. Whatever was changed in xorg to fix this apparently > requires a driver fix too. > > At any rate, I tested my ATI box and the results were as one might > predict: > > Radeon driver + Compiz: Works > FGLRX driver + Compix: Does not work > > I guess at this point I'll unsubscribe from this thread as any hope at > getting this fixed has now been lost, since it's going to be categorized > into that blackhole of "binary driver" issues. I hope whatever changes > xorg made to fix the original bug are somehow directly made known to all > driver vendors. > > -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
