My first guess was a recently introduced breakage/incompatibility in
glibc or similar library, but that sounds implausible as the bug also
manifests itself in etch (which other packages than libxml2 have changed
with the recent update in etch? none of the dependencies of Gnome apps,
right?).
My second guess would be a multithreading issue. So I've checked here
with one of the cores of the Core 2 duo disabled (and also with
frequency scaling set to fixed 2.5 Ghz as well as 800Mhz), but that
brought no change. (That doesn't preclude a multithreading issue; just
that people with a single-core CPU should generally be able to see the
problem too.)
I wonder if only people on 64bit machines are seeing the problem? Maybe
everyone contributing to the bug report could mention which kind of CPU
they are testing on and whether they can reproduce the issue or not.
Christian.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
