fixed in jaunty's ubuntu10
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Fix Released
--
Gnome Sound Properties failing with autodetect
https://bugs.launchpad.net/bugs/302699
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
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.
** Tags added: likely-dup
** Changed in: pulseaudio (Ubuntu)
Status: New => Incompl
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?
--
Gnome Sound Properties failing with autod
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.
--
Gnome Sound Properties failing with autodetect
https://bugs.launchpad.net
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.
--
Gnome Sound Properties failing with autodetect
https://bugs.launchpad.net/
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
--
Gnome Sound Properties failing with autodetect
https://bugs.launchpad.net/bugs/302699
You received this bug notification because you are a
gstreamer didn't change a lot between intrepid and jaunty that suggest a
pulseaudio issue rather
** Changed in: pulseaudio (Ubuntu)
Sourcepackagename: gstreamer0.10 => pulseaudio
--
Gnome Sound Properties failing with autodetect
https://bugs.launchpad.net/bugs/302699
You received this bug notifi
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
**
