On 9/1/05, Matthias Grimm <[EMAIL PROTECTED]> wrote: > > 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.
Then what's the point of the option in question (OSS_mixer), if pbbuttonsd assumes /dev/mixer, anyway if the selected sound system is OSS? What if I have two sound cards and I want to use /dev/mixer2 ? > 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. Ok, I understand; but /dev/mixer2 (see details above) should work. The first check should be done for the device I set in OSS_Mixer, not the assumed /dev/mixer (aka user's configs have higher priority over the assumed ones) > > > 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 I was reiterating the sound issue :) ; _that_ kind of errors > 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. OTOH, as a general idea, if parts of the functionality can't be initialized, then the core functionality (which initiates correctly) should be available. Thanks for your work! -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein
