Anytime I start MATE the access to sound devices becomes very slow,
even just doing `aplay -l` takes 4 seconds.

Similarly:

user@debian:~$ mate-volume-control

(mate-volume-control:101829): libmatemixer-alsa-WARNING **: 03:40:51.386: Failed to load mixer elements for hw:1: Connection timed out

(mate-volume-control:101829): GLib-GIO-WARNING **: 03:41:11.866: Your application did not unregister from D-Bus before destruction. Consider using g_application_run().

(mate-volume-control:101829): Gtk-CRITICAL **: 03:41:11.902: gtk_main_quit: assertion 'main_loops != NULL' failed

(mate-volume-control:101829): libmatemixer-alsa-WARNING **: 03:41:22.106: Failed to load mixer elements for hw:1: Connection timed out

almost forever.


This is with pulseaudio not running.

user@debian:~$ sudo lsof /dev/snd/*
lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
      Output information may be incomplete.
COMMAND      PID USER   FD   TYPE DEVICE SIZE/OFF      NODE NAME
mate-sett 101758 user   17u   CHR  116,6      0t0 127703736 /dev/snd/controlC0
mate-sett 101758 user   18u   CHR 116,14      0t0  72716494 /dev/snd/controlC2
mate-volu 101809 user   11u   CHR  116,6      0t0 127703736 /dev/snd/controlC0
mate-volu 101809 user   12u   CHR 116,14      0t0  72716494 /dev/snd/controlC2
mate-volu 101829 user   11u   CHR  116,6      0t0 127703736 /dev/snd/controlC0
mate-volu 101829 user   12u   CHR 116,14      0t0  72716494 /dev/snd/controlC2
mate-volu 101829 user   13u   CHR  116,3      0t0   6682191 /dev/snd/controlC1
mate-volu 101829 user   14u   CHR  116,3      0t0   6682191 /dev/snd/controlC1
user@debian:~$

$ time aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: M20 [MIYO USB Audio 2.0], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

real  0m3.961s
user  0m0.004s
sys 0m0.000s
$


Same from root.

If I logout out of MATE and execute `aplay -l` from terminal as normal user or
root, it finishes in 20 miliseconds.

Rest of alsa configuration is standard Debian config.

Hi, 
Is this still an issue? I am on Debian Sid and see no issues mentioned. Please see details below.

sv@sid-vm:~$ sudo lsof /dev/snd/*
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1010/gvfs
      Output information may be incomplete.
lsof: WARNING: can't stat() fuse.portal file system /run/user/1010/doc
      Output information may be incomplete.
COMMAND    PID USER FD   TYPE DEVICE SIZE/OFF NODE NAME
pipewire  1466   sv 56u   CHR  116,1      0t0  361 /dev/snd/seq
pipewire  1466   sv 57u   CHR  116,1      0t0  361 /dev/snd/seq
wireplumb 1470   sv 23u   CHR  116,5      0t0  596 /dev/snd/controlC0
sv@sid-vm:~$ time aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

real	0m0.005s
user	0m0.004s
sys	0m0.000s

Also, I see no errors when I start `mate-volume-control' from terminal.

sv@sid-vm:~$ dpkg -l libmatemixer0
┌── Desired=Unknown/Install/Remove/Purge/Hold
│┌─ Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
││┌ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
│││ Name                Version      Architecture Description
├┼┼─═══════════════════─════════════─════════════─═════════════════════════════>
ii  libmatemixer0:amd64 1.26.1-1+b3  amd64        Mixer library for MATE Desktop

Even on oldoldstable, the version is 1.24.1-1.

So, if the issue is not reproducible in any supported versions, may be we can close the issue?!

Hi Sui Vue,

I agree. Let's close this bug. I haven't seen anything like it within
the past years. Let's assume it got fixed in 1.24.1-1 (rather since
1.24.1-1, but well...).

Mike