Hi, > I tried to force, but the result was the same: > # pbbuttonsd -c /etc/pbbuttonsd.conf > ERROR: Can't open mixer device [/dev/mixer]. No such file or directory > INFO: Soundsystem requested: OSS and at least activated: none.
you could tell pbbuttonsd which sound system to use with the configuration option "SoundSystem". Depending of this setting other configuration options will be used. For example if you set this option to "OSS", "OSS_Mixer" will be read and "ALSA_Mixer will be ignored. Changing the option "ALSA_Mixer" in this context won't have any effect. If you set "SoundSystem = OSS" pbbuttonsd assumes indeed there is a /dev/mixer device and will complain if it is not there. This is not a bug. There are four possible options to set as SoundSystem: None Use no sound system at all OSS Use OSS, (Dev/mixer must exist) ALSA Use ASLA, (libasound must exist) AUTO Find the sound system to use automatically > Restarting pbbuttonsd: No /usr/bin/pbbuttonsd found running; none > killed. ERROR: Can't open mixer device [/dev/mixer]. No such file or > directory > > Well, that is odd; anyway, I could set the device to dev/null. Setting OSS_Mixer = /dev/null won't work, because it is not a mixer device and won't behave like a mixer device. Open the device will work but it won't report supported channels or the current volume and this will cause pbbuttonsd to detect an error. You better should set SoundSystem = AUTO. > Even if the reading was correct, ppbbuttons should not fail to load, if > there is no sound system present. This is a point which I could aggree. Currently pbbuttonsd complains about a missing sound device and quit. I think this is the wrong reaction, too. I changed the code so that the daemon would not exit if the configured sound system couldn't be initialized and the ERROR messages are turned into WARNINGs. > Pbbuttonsd should start even if there are errors; I can't agree to this. If pbbuttonsd detects an error, this mostly will have a major impact on functionallity (except the sound system errors). In other words: The daemon can't fullfill it's task if the underlying functions won't work correctly. In this case it is better to do nothing than to do it half or wrong. Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]