True, but the issue duplicated from 445435, and easily reproducible is the now linked gtk bug. I our case there is no memory or CPU spin like 460710.
I am interested to know if there is insight as to why the patch was not effective given the upstream resolution.
For now, we are sticking to Crux :) _ it reminds me of a purple Woody.
On Mon, 2009-11-02 at 21:31 +0000, Sebastien Bacher wrote: > the issue some users are having could be bug #460710 too >
True, but the issue duplicated from 445435, and easily reproducible is
the now linked gtk bug. I our case there is no memory or CPU spin like
460710.
I am interested to know if there is insight as to why the patch was not
effective given the upstream resolution.
For now, we are sticking to Crux :) _ it reminds me of a purple Woody.
On Mon, 2009-11-02 at 21:31 +0000, Sebastien Bacher wrote:
> the issue some users are having could be bug #460710 too
>