Michael,
So the cause of random mci time-out on test.winehq may as
well lay elsewhere.
Like in PulseAudio? That may well be. PA in F11 made sound be more
broken in Wine.
Is that your own experience or other people's reports?
My experience with PA in Ubuntu Intrepid -- it's not the newest Ubuntu
joerg-cyril.hoe...@t-systems.com wrote:
Michael,
So the cause of random mci time-out on test.winehq may as
well lay elsewhere.
Like in PulseAudio? That may well be. PA in F11 made sound be more
broken in Wine.
Is that your own experience or other people's reports?
My own from running
Hi,
Testhq.org results from 17th of November about winmm:mci were striking:
All machines producing a timeout had f11 in their name.
(Another day, some f11 machines passed the tests).
http://test.winehq.org/data/4990ca0ea342bd115a9a46047b3b2de599cb916e/index_Wine.html
Please test whether the
Hello!
joerg-cyril.hoe...@t-systems.com wrote:
Testhq.org results from 17th of November about winmm:mci were striking:
All machines producing a timeout had f11 in their name.
(Another day, some f11 machines passed the tests).
pulseaudio occasionally gets into a confusion by itself. I found I need to do
pulseaudio --cleanup-shm
from time to time.
--- On Thu, 19/11/09, joerg-cyril.hoe...@t-systems.com
joerg-cyril.hoe...@t-systems.com wrote:
Hi,
Testhq.org results from 17th of November about winmm:mci
were
