Ubuntu
alsa-driver package

Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.

Bug #1568772 reported by dino99
58
This bug affects 13 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Get that error logged into journalctl, on a fresh xenial 64 bits installed from mini.iso and sharing a /home partition with a wily installation. No third party package, only genuine default install.

Note that sound has no trouble; only this logged.
There is no sound card on this system, only a mobo chipset.

 systemd-udevd[412]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
systemd-udevd[407]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.

Maybe its related to the 'i' aka '--no-init-fallback' found here:
http://manpages.ubuntu.com/manpages/wily/man1/alsactl.1.html

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: oem 1755 F.... pulseaudio
 /dev/snd/pcmC0D0p: oem 1755 F...m pulseaudio
 /dev/snd/controlC0: oem 1755 F.... pulseaudio
CurrentDesktop: GNOME
Date: Mon Apr 11 13:50:55 2016
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

See original description
Revision history for this message
dino99 (9d9) wrote :
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
astro (bernard-godard) wrote :

I also have this problem.

It actually prevents restoring alsa mixer settings on boot.

The system starts with headphone muted. Using alsamixer, I can unmute and set headphones volume. Then I save the settings using alsactl store (also tried sudo alsactl store)
Preferences get saved in /var/lib/alsa/asound.state

But after reboot the headphones are muted again.
Running in a terminal alsactl restore or sudo alsactl restore unmutes the headphones and set their volume to the saved value, but adding alsactl restore in /etc/rc.local does not help.

Revision history for this message
astro (bernard-godard) wrote :

Adding sleep 10 in /etc/rc.local before alsactl restore does not help.

Contrary to what I said in my previous email in my last try running in terminal "sudo alsactl restore" did not manage to restore the mixer settings (even though there were no warnings or error messages) but "alsactl restore" (no sudo) did.

Alberto Salvia Novella (es20490446e)
Changed in alsa-driver (Ubuntu):
importance: Undecided → High
importance: High → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.