On Thu, Sep 09, 2010 at 07:15:29PM +0200, Sebastian Dröge <sl...@circular-chaos.org> wrote: > On Thu, 2010-09-09 at 19:11 +0200, Josselin Mouette wrote: > > Le jeudi 09 septembre 2010 à 18:54 +0200, Mike Hommey a écrit : > > > > I suggest we remove this “fix” according to the last commends in > > > > #495620. > > > > > > Great, so now we have the choice between CPU usage going up, or > > > iceweasel becoming unuseable thanks to X.org driver bugs... > > > > > > Please don't tell me I should start using the bundled version of > > > cairo... > > > > Could we at least circumvent the damage to iceweasel? This could be done > > in the ugly way by checking an environment variable that is set only by > > iceweasel. > > Yes, inverting the logic of the Mozilla cairo patch and then setting an > environment variable in iceweasel seems to be the best idea so far.
Except it will also propagate to any application launched from iceweasel. Still better, but still half broken. > And after squeeze release I'll immediately revert this annoying patch > again... Do you want to bet it will again be needed on wheezy ? While you're here, if you have ideas for #595200 and #593844... Cheers, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
