Final follow-up for my bug report: http://bugs.debian.org/682308 A bit late one. Sorry for that.
On Sat, Aug 4, 2012 at 12:35 AM, Przemysław Pawełczyk <prze...@gmail.com> wrote: > Just a follow-up. According to the comment of Pierre-Loup A. Griffais at > > cairo: [nvidia-302] Slow chromium tab switching with cairo-1.12.0 > https://bugs.freedesktop.org/49534 > > the issue should be resolved with the driver 304.30. Copy-pasting > relevant part of debian changelog: > > - Fixed a problem where RENDER Glyphs operations would exhibit severe > performance issues in certain cases, such as when used with gradients > by Cairo and Chromium. > > It's not yet in unstable, but when it'll get there, I'll try to check > this and confirm. Jindrich Makovicka already confirmed at the > mentioned bugtracker that new driver fixes the problem. Jesse Davis already confirmed that 304.37 worked fine for him. I have: 1. installed libcairo2 1.12.2-2 from wheezy (was using custom build with a workaround before), 2. rechecked that my Chrome browsing experience is in no way bearable, 3. installed nvidia-* stuff in version 304.48-1 from sid, 4. noticed that browser is responsive again! So it just works. No need to build your own libcairo2 and pin it anymore. > The issue affects a lot of people, thus I think that the best solution > would be the new nvidia driver hitting wheezy before it'll be released > as a stable. I believe that Wheezy will have nvidia stuff in 304.x version. Regards. P.S. Just in case, I'm CCing all participants of this bug discussion. -- Przemysław 'Przemoc' Pawełczyk http://przemoc.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org