[Bug 22127] New: artsd -D device option takes "hw:0, 0" but rejects "/dev/dsp", contrary to documented usage

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=22127
Ubuntu | arts

           Summary: artsd -D device option takes "hw:0,0" but rejects
                    "/dev/dsp", contrary to documented usage
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: arts
        AssignedTo: jriddell at ubuntu.com
        ReportedBy: adrian-bugzilla at groves.ca
         QAContact: kubuntu-bugs at lists.ubuntu.com


To use a non-default audio device in KDE device, the Sound&Multimedia Settings
interface "What's This" help says to try the device file: /dev/dsp, /dev/dsp1,
etc.  in the "Override Device Location" box.  This value is passed to artsd as a
-D option.  However, the error message returned by artsd is:

Sound server informational message:
Error while initializing the sound driver:
device: /dev/dsp can't be opened for playback (No such file or directory)
The sound server will continue, using the null output device.

even though /dev/dsp exists.  Omitting the argument (leaving the box unticked)
works and uses the default device, /dev/dsp.  However, setting the device to
"hw:0,0" or "hw:1,0" also works correctly (using /dev/dsp or /dev/dsp1).  This
is contrary to the usage message in "artsd -h":

-D <devicename>     audio device (usually /dev/dsp)

This might be correct behaviour, but it's wrongly documented in two places and
causes hours of confusion.

I'm using a clean install of Kubuntu 5.10 with only a couple of extra packages
installed (firefox, mp3 support).

Don't hesitate to contact me for extra information!

- Adrian

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.