Re: How to Debug ALSA on KDE Plasma 5 (Pulseaudo in the way?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Marc Haber wrote:
> And a week later, it stopped working again. Whatever I do,
> neither "mpg321 -o alsa -a hw:1,0" nor "mpg321 -o alsa -a hw:0,2" do
> something different than "Can't open libao driver with device hw:1,0
> (is device in use?)". I have chmodded /usr/bin/pulseaudio to 000 and
> killed the running daemon, and fuser /dev/snd/* doesn't output
> anything. Otoh, with an alsamixer running, fuser /dev/snd/* says that
> /dev/snd/controlC2 is in use by that process.

Doesn't mpg321 show the actual error code?
Oh well; does "strace -e open mpg321 ..." show any error code other than
EBUSY for the open("/dev/snd/pcm...")?


Regards,
Clemens

------------------------------------------------------------------------------
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user



[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux