From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922 Description of problem: Xmms playback skips when I run other programs, particularly when I open mozilla. The skips occur extemely often when I try to listen to music in the background while performing other tasks. Version-Release number of selected component (if applicable): xmms-1.2.7-22.1.p How reproducible: Always Steps to Reproduce: 1. Play a song in XMMS 2. Open Mozilla 3. Browse Actual Results: .25-1 second skips in song playback Expected Results: no skipping Additional info: This bug is similar to #100422 except I have the same problem in Enterprise Linux.
This is really related to kernel scheduling more than anything else.
I noticed that this is related with platform -- Athlon systems are experiencing skip/pause in playback; notable when disk is accessed. On Intel system, with less memory (1/4) and less MHz (1/2) XMMS is playing everything without problems.
Is xmms running at normal priority?
It happens also to me on an INTEL system 512 Mb RAM, centrino 1.5 Ghz But it is not only a skip but a completely paused when disk is accessed with FC4/xmms-1.2.10-16 The annoying thing is that the only way to reenable sound is pause/play the song or start a new one. The sound does not return after accesing the disk is finished. It had never happened before with FC3 xmms running with priority -2 in my system. No error message found. It happens with all fedora fc4 kernels and latest vanilla kernel.
See related bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196583 and patch https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=145501
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.