Your message dated Tue, 09 Apr 2019 16:33:37 +0000 with message-id <[email protected]> and subject line Bug#925455: fixed in alsa-utils 1.1.8-2 has caused the Debian Bug report #925455, regarding alsa volume never saved/restored to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 925455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925455 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: alsa-utils Version: 1.1.8-1 Severity: important File: /lib/systemd/system/alsa-restore.service Hi, On my newly installed laptop, the volume is never saved and restored It seems that the "alsa-restore.service" is never "started/stopped" because there is a condition not met: $ systemctl status alsa-restore.service ● alsa-restore.service - Save/Restore Sound Card State Loaded: loaded (/lib/systemd/system/alsa-restore.service; static; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Mon 2019-03-25 10:25:34 CET; 1h 15min ago Docs: man:alsactl(1) mar 25 10:25:34 edoras systemd[1]: Condition check resulted in Save/Restore Sound Card State being skipped. Looking a bit further it seems that /var/lib/alsa/asound.state doesn't exist. That means that we are facing a chicken-egg problem here, the file will never be created as the service is never started (and then never stopped). An option might be to create an empty file in the postinst script on the first installation. An empty file will cause the "alsa restore" command to fail with return code 99 but the systemd service will still be marked as "active (exited)" and the ExecStop will be executed on shutdown meaning that the volume will be saved. (Wouldn't that cause issue with some setup?) AFAICS, it's a regression and we might want to get this fixed in buster, if you think it should be the case, please make this bug RC. Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages alsa-utils depends on: ii kmod 26-1 ii libasound2 1.1.8-1 ii libc6 2.28-8 ii libfftw3-single3 3.3.8-2 ii libncursesw6 6.1+20181013-2 ii libsamplerate0 0.1.9-2 ii libtinfo6 6.1+20181013-2 ii lsb-base 10.2019031300 ii whiptail 0.52.20-8 alsa-utils recommends no packages. alsa-utils suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: alsa-utils Source-Version: 1.1.8-2 We believe that the bug you reported is fixed in the latest version of alsa-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Elimar Riesebieter <[email protected]> (supplier of updated alsa-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 9 Apr 2019 18:08:41 CEST Source: alsa-utils Binary: Architecture: source Version: 1.1.8-2 Distribution: unstable Urgency: medium Maintainer: Debian ALSA Maintainers <[email protected]> Changed-By: Elimar Riesebieter <[email protected]> Description: Closes: 925455 Changes: alsa-utils (1.1.8-2) unstable; urgency=medium . * Introduce Fix-alsactl-to-restore-config.patch. Don't rely on undocumented /etc/alsa/state-daemon.conf to start alsa-state.service. alsa-restore.service now will have an error code 99 the first time it runs. But after an reload of the service or just a reboot both services will run smoothly. [closes: #925455] Checksums-Sha256: f780bfea7fa29ad60b2d52e322dd759dd33698d9dc698df7559ede7678adb97a 2346 alsa-utils_1.1.8-2.dsc 7dc377276a9d78898fccbb96eacde0bf5a43eebfcf94521087c5b97cb70e7976 27076 alsa-utils_1.1.8-2.debian.tar.xz 98f61f079d52c3a563c438a35a5265aa5593c1aa4c00093ed5fec1f2e5404c7c 7778 alsa-utils_1.1.8-2_sourceonly.buildinfo Checksums-Sha1: 3f112124fc7bbd00bc825d2ee032a299f69ccc2f 2346 alsa-utils_1.1.8-2.dsc 7740418aa69666a976ea4a0df25fa95aaf422115 27076 alsa-utils_1.1.8-2.debian.tar.xz ac0e7e1a66c266a77f33979ead3fcfceb16be59e 7778 alsa-utils_1.1.8-2_sourceonly.buildinfo Files: 31a0af8bcf3b0dbbcc2cf3ba86959595 2346 sound optional alsa-utils_1.1.8-2.dsc fe2420b3a832c8e1e5ffe29977298932 27076 sound optional alsa-utils_1.1.8-2.debian.tar.xz 5049b7cab25445138f6d2887953cd39d 7778 - - alsa-utils_1.1.8-2_sourceonly.buildinfo -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlysw4pfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZeeQ/+IeqA4I8Ct/m/zGpRpwCLTn3oZ0KEbCqSZ8ejzwPMMhzuBVlFcL1wxdWX Ew0RV50p4P3C+W7oA6PsvgKv9tqxYAB/lLnrW1imDzNXBKYJV9sqx9I+8UwUKYzo MfKhBa8Zg4osRBX5rx/1vIZib9G7pZNH4NThmNpnOeujaPUxa6c4p9RgD425dVJq zL2f3gnEwCik4VmHjoPOq29LiFlP6sVhC5xrkkxoot5KN7xU4/kS0Rb9ZWE7z3IJ VJyqKbmQJ3XVFvpbOSbfG5QeV8BnC+7c8Sl/Ws4CAu+tBnyD0b7K+EPSPp54o/e+ TCvRo8uFnas2TIgI+tlaxyoh0SxOCecx8RZBwXB0OzDcK+kwykv1qSkOhGjzfJFp 9AndKlbF2TYwd51Gbdz0Xd642b9HDZ5XVfyo0idublaQtbDx5KMQWznqaYlJ9iQt q3Osy8WTeLXzreCCl09TVG4Y8W1T4xuNtuFvIIiQmSK5rWowIilzKuMHVXgEHfy4 RoXqKG0N2cXSvnD1Qf4NVzmAqy2waV0HrKPpwDlpFSKY7OitQPLil3uoae6zm1+n p1B8kVtjq+IsNx+/PrGzGXsToL8ltMW+5NviEsxW7ea2O3n9PQ2Z4SG65IACvwL5 dKq/kCj820CjgEI6rMMCq1d+2c3Ry374MdZ2YWNGPG9LZyjBkkw= =doq5 -----END PGP SIGNATURE-----
--- End Message ---
