I tried something quick against your points 2 and 3.
2) The wording is misleading me thinks. It isn't really a driver (these are
inside the kernel) but the accessing of the sound output.
3) applied.
Your point 1 is not clear to me. Do you see this message in a beautiful
artsmessage-box? Then it should be clear which soundserver is starting...
Or you see this on the console while kde is starting. Then its kde's
soundserver. Some lines above it should say that arts is starting...
To the CC'ed: is it okay to apply the attached patch?
Arnold
Index: artsd.cc
===================================================================
RCS file: /home/kde/arts/soundserver/artsd.cc,v
retrieving revision 1.49
diff -u -p -r1.49 artsd.cc
--- artsd.cc 29 Aug 2003 21:02:06 -0000 1.49
+++ artsd.cc 25 Sep 2003 17:04:45 -0000
@@ -294,16 +294,16 @@ int main(int argc, char **argv)
if(cfgForceStart && !AudioSubSystem::the()->check())
{
- warnNullDevice = "Error while initializing the sound driver:\n";
+ warnNullDevice = "Error while initializing the sound output:\n";
warnNullDevice += AudioSubSystem::the()->error();
- warnNullDevice += "\n\nThe sound server will continue, using the null output device.";
+ warnNullDevice += "\n\nThe sound server will continue, using the null output device /dev/null.";
AudioSubSystem::the()->audioIO("null");
}
if(!AudioSubSystem::the()->check())
{
- string msg = "Error while initializing the sound driver:\n";
+ string msg = "Error while initializing the sound output:\n";
msg += AudioSubSystem::the()->error();
arts_fatal("%s", msg.c_str());
exit(1);
