http://qa.mandrakesoft.com/show_bug.cgi?id=3014
Product: kdemultimedia Component: kdemultimedia Summary: KMix does not work, aumix does, since March 7 cooker update Version: 3.1-10mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] KMIx shows all controls at 100%, but no sound is heard. Running aumix you see that all controls are at 0. Setting the aumix controls to 70% causes sound to be heard. After the cooker update Friday evening, my working sound system didn't produce any sound. It changed my sound card driver, and KMix showed a crossed out speaker symbol in the system tray. I think 2987 relates to this error, as it describes the behavior of KMix. Pertinent information, gathered once I had everything working using aumix. kdemultimedia-3.1-10mdk lspcidrake -v | grep AUDIO audigy : Creative Labs|EMU10K2 Audigy Audio Processor [MULTIMEDIA_AUDIO] (vendor:1102 device:0004 subv:1102 subd:0053 grep sound-slot /etc/modules.conf alias sound-slot-0 snd-emu10k1 alias sound-slot- snd-emu10k1 lsmod | grep snd snd-pcm-oss 43556 0 snd-mixer-oss 14488 1 [snd-pcm-oss] snd-emu10k1 69268 5 snd-rawmidi 17600 0 [snd-emu10k1] snd-util-mem 3008 0 [snd-emu10k1] snd-pcm 77536 0 [snd-pcm-oss snd-emu10k1] snd-timer 18376 0 [snd-pcm] snd-page-alloc 7732 0 [snd-emu10k1 snd-pcm] snd-hwdep 6368 0 [snd-emu10k1] snd-ac97-codec 40160 0 [snd-emu10k1] snd-seq-device 5832 0 [snd-emu10k1 snd-rawmidi] snd 40868 4 [snd-pcm-oss snd-mixer-oss snd-emu10k1 snd-rawmidi snd-util-mem snd-pcm snd-timer snd-hwdep snd-ac97-codec snd-seq-device] soundcore 6276 0 [snd] chkconfig --list sound sound 0:off 1:off 2:on 3:on 4:on 5:on 6:off chkconfig --list alsa alsa 0:off 1:off 2:off 3:off 4:off 5:off 6:off aumix -q vol 70, 70, P bass 50, 50 treble 50, 50 pcm 70, 70 speaker 70, 70 line 70, 70, P mic 0, 0, R cd 0, 0, P igain 0, 0 line1 0, 0, P phin 0, 0, P video 0, 0, P fuser -v /dev/dsp USER PID ACCESS COMMAND /dev/dsp paul 2209 f.... artsd ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.