FS#9982 - alsa 1.0.16: alsactl restore returns an error

Attached to Project: Arch Linux
Opened by Filip Wojciechowski (fwojciec) - Thursday, 27 March 2008, 13:50 GMT
Last edited by Greg (dolby) - Saturday, 17 May 2008, 08:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Aaron Griffin (phrakture)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Running alsactl restore (or starting/restarting alsa daemon) produces the following error:

alsactl: set_control:1300: incompatible field type for control #42

Other than that there are no immediately apparent issues -- the sound is still playing.
Sound card: Chaintech AV-710 (ICE1724 driver)

Additional info:
alsa-lib 1.0.16-1
alsa-utils 1.0.16-1

Here is my /etc/asound.state: http://pastebin.ca/959445
Here is my /etc/asound.conf: http://pastebin.ca/959451
Here is my ~/.asoundrc: http://pastebin.ca/959453
Here is the output of "lsmod | grep ^snd": http://pastebin.ca/959454

Steps to reproduce:
run "alsactl restore" (on my hardware)

NOTE: Since this is something that will probably have to be fixed upstream I submitted a bug report to alsa tracker as well. Here is the link: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3870
This task depends upon

Closed by  Greg (dolby)
Saturday, 17 May 2008, 08:25 GMT
Reason for closing:  Upstream
Comment by Aaron Griffin (phrakture) - Thursday, 27 March 2008, 17:36 GMT
To be clear, it *does* restore the volumes properly, just has some ugly output?
Comment by Filip Wojciechowski (fwojciec) - Thursday, 27 March 2008, 18:13 GMT
That's right.
Comment by Aaron Griffin (phrakture) - Thursday, 27 March 2008, 19:13 GMT
Hmmm, so all things considered, ugly output is good as it lets us all know there's an upstream issue.

Comment by Jan de Groot (JGC) - Thursday, 27 March 2008, 23:36 GMT
Did you try restoring it, then storing it and then restoring it again? These mixer controls change with every alsa driver or library update, so it doesn't look weird to me when you get such an error after any random alsa component update.
Comment by Filip Wojciechowski (fwojciec) - Friday, 28 March 2008, 11:04 GMT
I did try that. I also manually removed the state file, stored and tried restoring but the error appears every time.

Loading...