On 2014-10-23, David Coppa <dco...@gmail.com> wrote: > On Thu, Oct 23, 2014 at 3:06 PM, Stephane Tougard <steph...@unices.org> wrote: >> On Thu, Oct 23, 2014 at 01:04:04PM +0200, David Coppa wrote: >>> > I'm using Slackware 14.1 with fvwm2 and Chromium, I see no issue at all. >>> fvwm2 with or without a compositor (like xcompmgr or compton)?
BTW has anyone looked at writing a port for compton? It is meant to be much better than xcompmgr (from which it originally derived). >> Original version of the Slackware. xcompmgr is as well originally part >> of Slackware. >> >> >>> And what version of chromium? >> >> 33 > > This is an older (still gtk+2 based) version of chromium: it doesn't > have this bug. > The bug started manifesting itself, when they switched to the new > "Aura" toolkit (since version 37 iirc). It happened _after_ the switch to Aura which was in 36.0.1985.125 which is the version that will be in 5.6 release packages, that one was ok. Looking at chat logs, I first mentioned it in September, and I recall that the problem definitely existed with the version immediately before the "use GPU accelerated cross process image transport on openbsd as well" commit - as I was hoping that might fix it :-). I'm not totally sure because of the lock and lack of snapshots, but I think 36.0.1985.143 is probably okay.
