Package: alsa-utils Version: 1.2.3-1 Severity: normal X-Debbugs-Cc: riveravaldezm...@gmail.com
Dear Maintainer, * What led up to the situation? AFAICT, last system update (yesterday). * What exactly did you do (or not do) that was effective (or ineffective)? With alsamixer running in a separated terminal [F6: Sound Card : - (default)] I did `pulseaudio --kill`. * What was the outcome of this action? CPU starts to work a lot and non-stoping. Going to alsamixer and doing F6: select another Card (the '0' one, for instance) stops this hang. But then when trying to choose again '- (default)' I have this message: > Error > Cannot open mixer device 'default'. > Connection refused Which I suppose it's OK since PA is not running. If I do `pulseaudio --start` and try again alsamixer seems to recover ('default' appears again). * What outcome did you expect instead? Not high-CPU-hanging, I suppose. Thanks a lot. Best regards. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages alsa-utils depends on: ii kmod 27+20200310-2 ii libasound2 1.2.3.2-1 ii libatopology2 1.2.3.2-1 ii libc6 2.30-8 ii libfftw3-single3 3.3.8-2 ii libncursesw6 6.2+20200918-1 ii libsamplerate0 0.1.9-2 ii libtinfo6 6.2+20200918-1 ii lsb-base 11.1.0 alsa-utils recommends no packages. Versions of packages alsa-utils suggests: ii dialog 1.3-20190808-1 -- no debconf information