Gnome Sound Properties failing with autodetect

Bug #302699 reported by Noel J. Bergman
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

After resolving the issues reported in Bug 299093, I encountered a problem with the sound preferences applet. KevinM described similar behavior in https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/299093/comments/12.

When going to System->Preferences->Sound and attempting to test, the applet fails to generate sound if I take the default Autodetect values. If I attempt to cancel the test, the applet hangs and has to be killed.

HOWEVER, if I explicitly set ALSA or OSS (having installed oss-compat) rather than Autodetect, the playback tests all succeed. PulseAudio fails with "audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Failed to connect: Connection refused."

gnome-control-center 1:2.24.0.1-0ubuntu7.1
pulseaudio* 0.9.13-2ubuntu1

Tags: likely-dup
Revision history for this message
Sebastien Bacher (seb128) wrote :

that's rather a gstreamer issue

Revision history for this message
Sebastien Bacher (seb128) wrote :

how do you know the issue is specific to jaunty? did you try on intrepid using the same configuration?

Changed in gstreamer0.10:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

I have exaclty the oposite error.
Autodetect works, Pulse Audio works, and Alsa says: audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=chat: Could not get/set settings from/on resource.

This is on jaunty.
I've seen a similar error on Ibex, but cant be sure of the sound subsystem or message in concrete.

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

logs attatched at bug 302781

Changed in gstreamer0.10:
status: Incomplete → New
Revision history for this message
KevinM (kevbert1) wrote :

In my case, regardless of the settings made (instead of Autodetect), I hear no audio at all on Jaunty kernel 2.6.27-7 64 bit. I'll check it on Intrepid and get back to you.

Revision history for this message
KevinM (kevbert1) wrote :

Intrepid Ubuntu kernel 2.6.27-7 64 bit works fine. I get a continuous tone when I click on Test with Autodetect. See attachment for settings... When I select IEC958 (ALSA) I get no sound. If I select NVidia CK804 (ALSA) and NVidia CK804 (OSS - 3rd one) I get no sound but the error:
audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Could not open audio device for playback.
Sound works fine for the other settings.
What logs/files do you need from Intrepid ? It seems strange that I have three sets of OSS settings which on first inspection look the same.

Revision history for this message
KevinM (kevbert1) wrote :

Sorry, forgot the screenshot...

Revision history for this message
Noel J. Bergman (noeljb) wrote :

> how do you know the issue is specific to jaunty?

Because I've tested going back to 8.04.1? I could tell you about 7.10, but I don't have it installed anymore.

> did you try on intrepid using the same configuration?

Yes. Works as expected using any of Autodetect, OSS, ALSA and PulseAudio.

Revision history for this message
Sebastien Bacher (seb128) wrote :

don't specify the version in the title anyway that creates extra work and confusion, some gutsy bugs are still open and such title would suggest the issue is specific to version in the title where it's the version where the bug has been opened, you can use the description to specify the version

Revision history for this message
Sebastien Bacher (seb128) wrote :

gstreamer didn't change a lot between intrepid and jaunty that suggest a pulseaudio issue rather

Revision history for this message
Sebastien Bacher (seb128) wrote :

you can try to downgrade the pulseaudio version to the intrepid one rather than downgrading the distro and try if that's still an issue when using this one

Revision history for this message
KevinM (kevbert1) wrote :

Sound has been fixed for me in Jaunty (still kernel 2.6.27-7, so it must have been one of the updates that sorted it out). Autodetect works fine, thanks. I'll check Intrepid to see if that now works and get back to you.

Revision history for this message
KevinM (kevbert1) wrote :

One this that doesn't seem to work in Jaunty is that there is no startup sound even though the sound setting is set to default (is this a new bug ?) Intrepid is working fine with Autodetect and there is a startup sound.

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

i'm in doubt if I should file a new bug...
For me, as i mentioned on https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/302699/comments/3 its the oposit.

Autodetect and PA work fine.
Alsa gives me the error.

What do u think seb128? new bug?

Revision history for this message
Daniel T Chen (crimsun) wrote :

bugabundo, you should use gst-launch-0.10 with alsasink and increased debugging verbosity (level 3 as a maximum for suggestion, since anything higher is too low of a S/N ratio), then attach the output here.

Changed in pulseaudio:
status: New → Incomplete
Revision history for this message
Daniel T Chen (crimsun) wrote :

fixed in jaunty's ubuntu10

Changed in pulseaudio:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.