Do you perhaps have any /etc/asound.conf or .asoundrc or similarly named files messing up your sound config?
Additionally (another wild guess), try running aplay -l -L and report the output. On Thu, May 5, 2022, 16:00 Pascal via arch-general < arch-general@lists.archlinux.org> wrote: > I checked in my session the concurrent accesses with fuser -v /dev/snd/* > and killed the only one that was present and could interfere (volumeicon > *that > was also present with Firefox and Mplayer*). > > Le jeu. 5 mai 2022 à 15:50, Pascal <patate...@gmail.com> a écrit : > > > Alsa directly : no PA or PW. > > > > when i run Chromium from a terminal, i get these two error messages about > > Alsa but they also appear when the sound is working : > > [4765:4765:0504/164956.649650:ERROR:alsa_util.cc(204)] PcmOpen: > > default,Device or resource busy > > [4765:4765:0504/164956.649811:ERROR:alsa_util.cc(204)] PcmOpen: > > plug:default,Device or resource busy > > > > Le jeu. 5 mai 2022 à 15:46, Jesse Jaara via arch-general < > > arch-general@lists.archlinux.org> a écrit : > > > >> Are you using Alsa directly, no pulseaudio or pipewire? Something could > be > >> wonky with your dmix config and it's getting disabled, thus only a > single > >> application can have access to the sound playback at once. > >> > > >
