Hello everybody out there!
On 2020/01/05 7:25 pm, Andrei POPESCU wrote:
> As someone else mentioned, possibly some other process is keeping the
> audio device busy. 'lsof | grep /dev/snd/' (as root) should help.
Yes, why have I not done this before?
# lsof | grep /dev/snd/
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
alsactl 573 root 4r CHR
116,7 0t0 16293 /dev/snd/controlC0
timidity 861 timidity mem CHR
116,2 16230 /dev/snd/pcmC0D0p
timidity 861 timidity 3r CHR
116,33 0t0 12983 /dev/snd/timer
timidity 861 timidity 4u CHR
116,2 0t0 16230 /dev/snd/pcmC0D0p
timidity 861 timidity 5u CHR
116,7 0t0 16293 /dev/snd/controlC0
timidity 861 timidity 6u CHR
116,1 0t0 12984 /dev/snd/seq
Now, this is interesting, as some reported troubles between Timidity
and Pulseaudio (e.g. https://bbs.archlinux.org/viewtopic.php?id=154002).
I have no problem with Timidity and Pulseaudio on other Debian 10
systems, as well on Fedora or Ubuntu. Anyway, I should investigate this.
Best regards.
--
Yoann LE BARS
http://le-bars.net/yoann/
Diaspora* : yleb...@framasphere.org
