gnome-sound-properties gives error when testing HDA ATI SB ALC1200 Analog (ALSA) sound

[Allan Bogh]

Binary package hint: gnome-control-center

Error report states:

audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=music:
Could not open audio device for playback.

If the device cannot be used then it should not be listed as an option for testing. If it cannot be opened due to some other reason then a simple explanation or troubleshooting method should be provided. If it is a fatal error with the device then a detailed report should be provided, but hidden from normal view so that the average Joe doesn't get scared.

The thing about it is I've selected this device for use even though I can't test it, but it still seems to work because sound works fine in every program except Totem (which I've reported as a different bug, possibly related, maybe not).

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-sound-properties
NonfreeKernelModules: fglrx
Package: gnome-control-center 1:2.26.0-0ubuntu3
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
Uname: Linux 2.6.28-11-generic x86_64

[Sebastien Bacher (seb128)]

the software can't know what options are working on not without trying those and you probably don't want random sound played when started the configuration tool only for that

[Allan Bogh (ajbogh)]

Respectfully, I don't entirely mind the drop-down displaying several options that might not work, but when I hit the Test button then it should tell me in plain English (or a localization alternative) that it couldn't complete the test for whatever reason. It shouldn't pop up a dialog box displaying weird error information like:

   audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=music:
   Could not open audio device for playback.

Also, since I continue to keep the option selected, even after the test fails, I can only assume that my computer is using this option. The sound works with this option selected, so why would the error come up at all?

FYI: OSS works with the Test button, but ALSA does not work when hitting the Test button. If I select ALSA without testing it then the sound works fine on the system.

In response to your comment, the software should be able to know what options are available by reading what drivers are in use, or what options are used with those sound drivers. You can also use a wizard to configure all of the sound options. "<Click here> to test your sound, white noise will be sent to the speakers, please reduce the volume before clicking".

[Sebastien Bacher (seb128)]

right the error message could be cleared

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GStreamer is available in both Lucid and Maverick and we are wondering if this is still reproducible in any of those versions, May you please test and give us of feedback about it? Thanks in advance.

[Allan Bogh (ajbogh)]

When using gstreamer-properties the message:

        ALSA - Advanced Linux Sound Architecture:
        Could not open audio device for playback.
        Device is being used by another application

is very helpful (Plugin ALSA, Device ALC1200 Analog). Although, if I
click ALC1200 Digital, then click test, no sound comes out, which is
expected. If I click back to Analog then the sound plays normally. This
is confusing if the original error message states that the device is in
use. Is it being mounted at the time? Should the system wait until it's
been fully opened?

Apparently this only happens if I switch from Default to Analog. If I go
from Analog to Digital, then back to Analog then the device can be
opened and plays the test sound. The same error occurs if I go from
Default to Digital, then to Analog. I have to go from Analog to Digital
then back to get the error message to go away.

OSS works fine. PulseAudio works as well on both Default and Unknown
(why "Unknown"?)

Hope this helps.

Allan Bogh

On Fri, 2010-07-02 at 16:05 +0000, Pedro Villavicencio wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. A new version of GStreamer is available in both Lucid and
> Maverick and we are wondering if this is still reproducible in any of
> those versions, May you please test and give us of feedback about it?
> Thanks in advance.
>
> ** Changed in: gstreamer0.10 (Ubuntu)
> Status: New => Incomplete
>

[Launchpad Janitor (janitor)]

[Expired for gstreamer0.10 (Ubuntu) because there has been no activity for 60 days.]