Version: 3.5 (using 4.2.3 (KDE 4.2.3), Debian packages) Compiler: cc OS: Linux (x86_64) release 2.6.29-2-amd64 Reported by: Filipus Klutiero <cheal@hotpop.com> From: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407598 By default, kmix setting "Restore volumes on login" is enabled. I recognize that this might be useful in certain situations, but this should be disabled by default. I believe this should be changed upstream, but it should at least be changed in Debian, which uses ALSA by default. ALSA already deals with mixer levels restoration through alsactl [re]store and /etc/init.d/alsa-utils. Having kmix mess with this by default means that the procedure documented in section "Storing mixer levels" of /usr/share/doc/alsa-utils/README.Debian is not enough to disable mixer levels storage. It's also quite clear that the init script is best to handle this, as shown by the following experiment: 1. Create 2 users 2. Login with user 1, set master to, say, 50%. Logout 3. Login with user 2, mute master. Logout 4. Save kmix config for both users. Case A 1. Login with user 1. 2. Login with user 2. Observe that master is mute. Case B (restore kmix config saved at step 4) 1. Login with user 2. 2. Login with user 1. Observe that master is set to 50%.
Well, this is a distribution decision - some distributions don't restore volume at all in init.d. So I need to do that, because I am tired of "All volume controls are zero" Bugreports. So if Debian would think, KMix volume restauration is a bad thing, they could change it in the global KMix config file. Also, volume levels are a per-user setting. Example: If one user regular listens via headphone, and the other via speakers you simply MUST change voulmes and switches accordingly. So you see that no solution here will be 100% perfect. All in all: I intend to keep the default. Just change the option locally. An Syadmin could even change the default in the global KMix config file.
We in Debian try to keep as close to upstream as possible. So, if your decision is to keep the default, we will be keeping it :-) Regards, Lisandro.
Yes, I am keeping it. It is generating too many other bugreports if I do not do it.