I haven't been able to find the time to run the upgrade or anything like it.
I will, but not right now. I should just give up and use a live cd...
I just tested out the Meerkat Beta on a CD on this machine. The behaviour
from the live CD is still not what I want, but at least it has changed :-).
** Changed in: gstreamer
Status: Invalid => Unknown
** Changed in: gstreamer
Importance: Unknown => Critical
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of U
Angus: did your upgrade work?
Can anyone reproduce this bug on any currently supported Ubuntu release? (9.04
or later)
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of U
I am now able to update the laptop I originally reported over. The
upgrade is running right now. I will report ASAP.
I needed a standby OS for the other users... Flash games :-)
2009/12/17 Przemysław Kulczycki :
> Gutsy is EOL now.
> Can anyone confirm if this bug still appears in latest Ubuntu r
Gutsy is EOL now.
Can anyone confirm if this bug still appears in latest Ubuntu release? (9.10
Karmic)
** Changed in: baltix
Status: New => Incomplete
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug no
I will check. The laptop in question is not presently running ubuntu, but I
will boot a live cd to check.
On Sun, Jun 14, 2009 at 1:58 AM, Hew McLachlan
wrote:
> gstreamer is not the right sourcepackage, removing.
>
> Does this problem still occur with the latest Ubuntu release?
>
> ** Package c
gstreamer is not the right sourcepackage, removing.
Does this problem still occur with the latest Ubuntu release?
** Package changed: gstreamer (Ubuntu) => ubuntu
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this b
** Changed in: gstreamer
Status: New => Invalid
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
http://www.antonywilliams.com/2007/10/bash-script-to-automate-compiling-
alsa.html
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
try this tutorial, it works for me(hp nx7400) (for red hat like change
apt-get by urpmi )
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Using the following sound card:
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
Audio Controller (rev 02)
Fresh Hardy Heron Beta install, I am using the headphone and mic jack on
the front of the system to use my conventional headset.
The machine is a Gateway CX272
Hardy is going to be finished in two months, and it would be good if
everyone still experiencing this bug in Gutsy would burn a Hardy alpha 6
livecd, boot it up, and test your sound problems to see if they've been
resolved. Report your findings back here.
Even though I reported perfect sound capt
The same problem here
I tried three different devices, I even bought a new soundcard, but mic
does not work at all!
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubun
If you need special programs, which don't run under linux, like
speech-to-text programs or professional film-cut or the like, you have
the choice to install vmware-server (which is free) or another
virtualization program, which allows you to run windows safely under
linux. You may install vmware-se
One more point: The Ubuntu teamers are working very hard to fix any
bugs, so this problem might disappear very quickly as irt did with me by
the regular updates provided automatically. My audio system works fine now.
uga schrieb:
> As usual, your problem stems from the fact that you are trying to
As usual, your problem stems from the fact that you are trying to run
Linux on Windows hardware. Before buying any piece of hardware, first
make sure it works with Linux. Yes this is one more step you have to
go through that you normally don't have to with Windows, especially if
you are buying from
I have to agree.I'm a complete Linux (but not Unix) newbie. Having just
acquired an old system box I thought I'd give Linux a play, so put
Ubuntu Gutsy on it.
Then plugged in my USB sound card. Couldn't find anything about how to
configure sound cards, so tried recording. Was told that "Your audi
Same error here. creative labs external live! usb. Sound works, but
recording is no-go.
USB support should be PRIMARY anymore, and this is, well this is one of
the reasons folks stay with bug #1. (On XP, the usb microphone just
"works".)
--
[gutsy] no sound: Failed to construct test pipeline
May someone else confirm that it's working with latest update? thanks.
** Changed in: gstreamer (Ubuntu)
Importance: Undecided => Low
Status: New => Incomplete
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received
After todays update it magically worked (again - it worked under feisty
before). I am guessing it had to to with the update of libpulse0.
Now I have the same old problem that I hear myself over my headphones, but I
had that before and can live with it.
--
[gutsy] no sound: Failed to construct t
I was getting:
Failed to construct test pipeline for 'gconfaudiosrc ! audioconvert !
audioresample ! gconfaudiosink profile=chat'
The fix was really simple. I just double-clicked on the volume control
in Gnome (the little speaker icon next to the system clock). There I
enabled everything. Spec
I can duplicate the error message when testing sound capture in Gutsy,
but my audio capture works great. Also, I tested this in Hardy Alpha 3,
and it appears to be fixed as I can't reproduce the error message.
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs
I too get the
Failed to construct test pipeline for 'gconfaudiosrc ! audioconvert !
audioresample ! gconfaudiosink profile=chat'
error when testing sound capture, but I can he the recording. I am
using a USB webcam microphone on a Dell XMS M1210. I have tested the
mic with Skype echo and it wor
i had this problem also. I managed to fix by purging esound, esound-clients,
pulsaaudio-module-gconf and pulseaudio. After that I gave the computer a hard
reset and ... as if by miracle, IT WORKS.
Minor detail: after I've read through the comments here, I installed the
programs mentioned above a
I'm having this problem also on Ubuntu64 'gutsy'. I have
PulseAudio-0.9.6-1ubuntu-2 installed and configured. I've had one audio
problem after another with Ubuntu.
I installed PulseAudio originally to solve a problem I was having
getting flash audio to work in firefox, and PulseAudio solved that
p
I'm having the same problem also , i was able to record on feisty using
audacity but in gutsy 7.10 i can't record anything
also i cant hear the logout sound.
I hope that will be fixed soon.
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/
Same message with me ("Failed to construct test pipeline for 'gconfaudiosrc !
audioconvert ! audioresample ! gconfaudiosink profile=chat'"), recording-sound
works better after formating and reinstall , but quality (Alsa) is very poor in
my Gutsy-Gnome. Have installed vmware on it: there (with wi
in amsn i get the error:
[18:23:44] An error occured when trying to record the sound : Could not
open default for read.
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of
This only happened when i've installed the tv card... :(
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
** Also affects: baltix
Importance: Undecided
Status: New
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I just turned ESD off in the system > preferences >sound - sounds tab
Then turned everything on in Edit > preferences of "Volume Control: HDA Intel
ALSA Mixer", enable the Capture fader mute and toggle from capture on the
recording tab
Fired up JACK and voila, I could record my vocals from the pc
It appears that the error message
Failed to construct test pipeline for 'gconfaudiosrc ! audioconvert !
audioresample ! gconfaudiosink profile=chat'
(when testing the sound capture in GNOME/Ubuntu) is bogus.
I managed to get sound working (playback and recording) and I still get the
above gstrea
I'm using a generic USB headset I bought at RadioShack (which actually
has an amazingly good microphone) that worked with Feisty.
Before upgrade: All options in the sound panel were set to USB audio.
Default mixer tracks set to device C-Media USB Headphone Set (Alsa
mixer). Microphone, Microphone
Hi,
My micro is working again.
I have found out, that after the upgrade from feisty to gutsy, all capture
channels under gnome-volume-control --> edit->preferences were disabled. I have
never thought about that, assuming all preferences would be kept during the
upgrade.
But, whatever, I enabl
Every other boot up on both my computers sound will stop working, and I
get
audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample !
gconfaudiosink: Internal GStreamer error: state change failed. Please
file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
This is after
same here! Everything was working fine with feisty but not anymore with
gutsy! I cannot not confiugure the micro witho gnome and naturally the
micro is not working with skype or wengophone (but for this one I don't
have sound too).
--
[gutsy] no sound: Failed to construct test pipeline in sound r
same as above described here, with Gutsy as Beta now and the latest kernel from
a couple of hours ago:
2.6.22-14-generic.
Skype is unusable for now for me. :(
Hope this will get fixed soon.
** Attachment added: "Screenshot-gnome-sound-properties.png"
http://launchpadlibrarian.net/9904770/Sc
I have already described my problem as bug 114233. However, it got worse
now: I cannot even use OSS anymore. The mentioned work-around with
starting the pipeline manually does not work for me (or I do not
understand it correctly.
--
[gutsy] no sound: Failed to construct test pipeline in sound rec
I have a sound blaster live card as well as onboard sound. Sound is
working but recording is not with either card... i get the message
Failed to construct test pipeline for 'gconfaudiosrc ! audioconvert !
audioresample ! gconfaudiosink profile=chat
--
[gutsy] no sound: Failed to construct test pi
Both my computers are getting the:
Failed to construct test pipeline for 'gconfaudiosrc ! audioconvert !
audioresample ! gconfaudiosink profile=chat'
Is there a fix yet, if so did I miss it?
Thanks
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad
This guy filed a similar report, with what might be a workaround.
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/147298/
It seems to have gotten sound capture in Sound Recorder working for me
while this is running. I had to apt-get install gstreamer-tools and
execute this in a termina
I think my bug is #131133 actually, which I've managed to work around:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/131133/comments/73
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug noti
Same problem for me in Gutsy Beta.
$ aplay -l
aplay: device_list:204: no soundcards found...
$ lspci -v
...
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 02)
Subsystem: Dell Unknown device 0228
Flags: fast devsel, IRQ 20
Memory at f
Solved for me ! I was using a Gusty 32 bits on my Athlon 3000+ 64 bits
(Asus A8V-VM), and recently we had some kernels updates so Grub was
booting on a 2.6.22.xxx i386 (!) kernel. Booting the 2.6.22xxx Generic
kernel, sound works again. To prevent this, I finally downloaded the
25th Daily Build of
Same for me. Fresh Gutsy 5 install.
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubun
Me too. My laptop has 3 sound devices: Conexant CX8811 (Alsa mixer), HDA
Intel (Alsa mixer), and CX88 (OSS Mixer)
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
Same happens here. Everything worked fined in Feisty, in Gutsy doesn't. My
notebook is MSI S260 with ALC655 sound codec.
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member o
same here with Gutsy 5
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Same problems here
Gutsy up to date
Everything OK
after some upgrades () to linux kernel -> Internal GStreamer error: state
change failed. Please file a bug at
http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.
--
[gutsy] no sound: Failed to construct test pipeline in sound recordi
Same problem here.
I am running Gutsy Tribe 5 since two weeks, and sound worked perfectly
on my Asus A8V-VM motherboard until the recent updates this morning. I
remember there was kernel stuff inside, so I bet that's the problem
source.
--
[gutsy] no sound: Failed to construct test pipeline in s
Same problem here.
Had a working Feisty install on a Dell Inspiron 6000, upgraded to Gusty
== No sound
I have tried installing pulseaudio-esound-compat but it did not fix the
issue.
When I run the test in Preferences -> Sound I hear no sound and get no
error regardless of which device I s
My sound initially worked with a fresh Tribe five install but some
update later it stopped. I get this:
confaudiosrc ! audioconvert ! audioresample ! gconfaudiosink
profile=chat: Internal GStreamer error: state change failed.
--
[gutsy] no sound: Failed to construct test pipeline in sound record
Found same problem in Sony VAIO PCG-V505CP
when upgrading from 7.06 to somewhere around **Tribe 4** and beyond
(using **Update Manager** everyday, until 14 September)
So today I decided to make fresh install from 7.10 **Tribe 5 Live CD** -- and
the sound COME BACK.
from
http://support.vaio.son
Using Gutsy Tribe 5 on a Dell Inspiron 6000, sound is Intel ICH6 with
STAC9752,53
I was using and recorded guitar tracks with Audacity on Sept 6th through
the mic jack.
Today it won't record and it says,
Error while opening sound device. Please check the input device settings and
the project sa
** Summary changed:
- No Sound in Gusty
+ [gutsy] no sound: Failed to construct test pipeline in sound recording
--
[gutsy] no sound: Failed to construct test pipeline in sound recording
https://bugs.launchpad.net/bugs/131711
You received this bug notification because you are a member of Ubuntu
55 matches
Mail list logo
