Bug#407598: One more opinion.
El Sábado, 5 de Enero de 2008, escribió: Le January 4, 2008 09:33:45 pm Raúl Sánchez Siles, vous avez écrit : Hello Filipus: IMHO, I think you are mixing different concepts. One thing is system wide volume level which are stored on a system wide basis, previosluy with alsa-utils init script ( no longer present) Since when? I have to excuse since I've noticed I'm misleading, which is no longer present as init script is the alsa script now stored on /usr/sbin, it is related to module load/unload and settings but alsa-utils still deals with settings as well. BTW, what about the rest of the rationale? :) Thanks. -- Raúl Sánchez Siles -Proud Debian user- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
Bug#407598: One more opinion.
Le 4 janvier 2008, Raúl Sánchez Siles a écrit : Hello Filipus: IMHO, I think you are mixing different concepts. One thing is system wide volume level which are stored on a system wide basis, previosluy with alsa-utils init script ( no longer present) and another, different, thing is user level volumes. Once you power your system up you start it as system wide and hence the alsa init script do its work. Remember you are not forced to log in when you power on your computer. This would be the case for example a media center. After this, you are free to log in and there is where kmix is doing it's job. The problem as you say is when you shutdown. Well, it is certain that alsa will store the settings for the last user that changed them, but otherwise, alsa would have to take into account what user has the right to do these operations and remember it, this is not very handy. I don't understand this sentence. Since it's certain that alsa will store the settings for the last user that changed them, how can you write about a different situation?
Bug#407598: One more opinion.
Hello Filipus: IMHO, I think you are mixing different concepts. One thing is system wide volume level which are stored on a system wide basis, previosluy with alsa-utils init script ( no longer present) and another, different, thing is user level volumes. Once you power your system up you start it as system wide and hence the alsa init script do its work. Remember you are not forced to log in when you power on your computer. This would be the case for example a media center. After this, you are free to log in and there is where kmix is doing it's job. The problem as you say is when you shutdown. Well, it is certain that alsa will store the settings for the last user that changed them, but otherwise, alsa would have to take into account what user has the right to do these operations and remember it, this is not very handy. Also think that not all users can do that, only those in the audio group. Once a user is inside that group they would have to cope with each other, or alternatively disable alsa level storing as explained in the README.Debian file you stated. I think it's hard work for alsa to take into account each user actions and even more, it's not and shouldn't be its job. If you still think this is important and you have a good solution for it, feel free to explain, or even better make a patch ;) If you agree with me I think this bug could be closed. Thanks. -- Raúl Sánchez Siles -Proud Debian user- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
Bug#407598: One more opinion.
Le January 4, 2008 09:33:45 pm Raúl Sánchez Siles, vous avez écrit : Hello Filipus: IMHO, I think you are mixing different concepts. One thing is system wide volume level which are stored on a system wide basis, previosluy with alsa-utils init script ( no longer present) Since when?
