How about not installing alsactl. It shouldn't be needed and it's causing things like bug 180119. Perhaps just use flag it away.
canney do that -- it is required by the alsasound init script
(In reply to comment #1) > canney do that -- it is required by the alsasound init script > So you don't see it as a problem that it uses a different path? Shouldn't be too hard to fix?
I don't see it as a problem at all, as I explained on the other bug. Here are the 2 usage scenarios: 1. User uses alsasound init script configured to save and restore volumes (the default). User never touches alsactl. No problems regarding default state store locations are encountered, the user is potentially completely unaware of how alsasound does it's magic volume thing. This is what you'll get if you follow our official documentation. 2. User doesn't use alsasound init script, or uses it but has configured it not to mess with volume stuff. User implements their own volume control, probably by using alsactl. No problems regarding default state store locations are encountered (the user is 100% in charge here).
