Your message dated Thu, 01 May 2025 14:40:04 +0200 (CEST)
with message-id <20250501124004.e5c84be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #959170,
regarding linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with
exit code 99
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 ow...@bugs.debian.org
immediately.)
--
959170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.6.7-1
Severity: minor
With the 5.6.0-1-amd64 Linux kernel at least, I get the following
error at boot (shown by journalctl):
Apr 30 11:57:16 zira systemd-udevd[489]: controlC0: Process '/usr/sbin/alsactl
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with
exit code 99.
This apparently comes from /lib/systemd/system/alsa-restore.service,
which has:
ExecStart=-/usr/sbin/alsactl -E HOME=/run/alsa -E
XDG_RUNTIME_DIR=/run/alsa/runtime restore
It seems that the first time I got a similar error was in October:
Oct 22 10:07:58 zira systemd-udevd[500]: Process '/usr/sbin/alsactl -E
HOME=/run/alsa restore 1' failed with exit code 99.
Then in November:
Nov 10 02:40:42 zira systemd-udevd[513]: Process '/usr/sbin/alsactl -E
HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit
code 99.
/etc/alsa/conf.d contains:
lrwxrwxrwx 1 root root 44 2020-02-29 17:15:54 10-rate-lav.conf ->
/usr/share/alsa/alsa.conf.d/10-rate-lav.conf
lrwxrwxrwx 1 root root 46 2020-02-29 17:15:54 10-samplerate.conf ->
/usr/share/alsa/alsa.conf.d/10-samplerate.conf
lrwxrwxrwx 1 root root 45 2020-02-29 17:15:54 10-speexrate.conf ->
/usr/share/alsa/alsa.conf.d/10-speexrate.conf
lrwxrwxrwx 1 root root 48 2020-02-29 17:15:54 50-arcam-av-ctl.conf ->
/usr/share/alsa/alsa.conf.d/50-arcam-av-ctl.conf
lrwxrwxrwx 1 root root 40 2020-02-29 17:15:54 50-jack.conf ->
/usr/share/alsa/alsa.conf.d/50-jack.conf
lrwxrwxrwx 1 root root 39 2020-02-29 17:15:54 50-oss.conf ->
/usr/share/alsa/alsa.conf.d/50-oss.conf
lrwxrwxrwx 1 root root 46 2020-02-29 17:15:54 50-pulseaudio.conf ->
/usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
lrwxrwxrwx 1 root root 47 2020-02-29 17:15:54 60-a52-encoder.conf ->
/usr/share/alsa/alsa.conf.d/60-a52-encoder.conf
lrwxrwxrwx 1 root root 41 2020-02-29 17:15:54 60-upmix.conf ->
/usr/share/alsa/alsa.conf.d/60-upmix.conf
lrwxrwxrwx 1 root root 44 2020-02-29 17:15:54 60-vdownmix.conf ->
/usr/share/alsa/alsa.conf.d/60-vdownmix.conf
lrwxrwxrwx 1 root root 46 2020-02-29 17:15:54 98-usb-stream.conf ->
/usr/share/alsa/alsa.conf.d/98-usb-stream.conf
lrwxrwxrwx 1 root root 38 2020-02-06 03:06:41 99-pulse.conf ->
/usr/share/alsa/alsa.conf.d/pulse.conf
-rw-r--r-- 1 root root 201 2018-11-03 00:35:24
99-pulseaudio-default.conf.example
(I haven't changed anything there.)
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---
