http://qa.mandrakesoft.com/show_bug.cgi?id=2965
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2003-03-08 22:03 -------
The bug #2968 was a duplicate of this one so the conclusion is the same : the
problem did not come from artsd but from kernel ! An upgrade to 2.4.21-0.13mdk
solved it : in fact, the phenomena of "sound cut" appeared when there was a high
graphic use (moving windows, jumping from on desktop to another, scrolling ...).
Nevertheless, thanks for Pascal and cybercfo for their indications... but why a
real-time option if this one is not possible for a "standard" user ?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
The artsd process cannot be lanched with real-time priority (nice level always
at 0 even if you set "real-time" in the KDE config module). The consequence is
that the sound is cut and hashed when you move a window, open a program, or
anything that use CPU ressources (even if not 100% of your CPU is used - I have
this problem on a PIII866 with 256Mo RAM...)
