Comment 116 for bug 352732

It's a 3 years old bug which really should have been fixed by now. Instead of using workarounds I'd like to understand what's the root cause of the issue and get it fixed.

I've done as written in #63 to track this down and got:

2012-05-15 01:51:58 Running alsactl store
2012-05-15 12:11:28 Running alsactl restore
2012-05-15 12:11:28 Running alsactl restore 1
2012-05-15 12:11:28 Running alsactl restore 0
[muted and manually corrected]
2012-05-16 04:21:32 Running alsactl store
2012-05-16 15:01:49 Running alsactl restore
2012-05-16 15:01:49 Running alsactl restore 1
2012-05-16 15:01:49 Running alsactl restore 0
[muted and manually corrected]
2012-05-17 03:27:04 Running alsactl store
2012-05-17 12:41:22 Running alsactl restore 1
2012-05-17 12:41:22 Running alsactl restore 0
2012-05-17 12:41:22 Running alsactl restore
[muted and manually corrected]

According to /etc/init/alsa-restore.conf and /etc/init/alsa-store.conf instead of "restore 1", "restore 0" and "restore" only "restore" should be executed, right?

If anyone has any idea about the above or about the root cause of this issue please don't hesitate to share. This is a disturbing sucker that should be eliminated.