Yes, there is a couple of ways this can be gotten into hardy. Firstly
getting alsa-plugins and alsa-lib into hardy-backports, but that doesn't
help resolve the vast majority of possible similar cases to this one
that may be out there now, and in the future.
The second involves finding the
Could everybody experiencing this bug please try the package of
libasound2, and if you use libasound2-plugins, the package of
libasound2-plugins from intrepid, and reply stating whether the issue
goes away when using these newer packages?
i386:
And I used to be a Gnome advocate and have used it for years. Now I'm
telling everyone to stay away from it
go troll somewhere else, nautilus is not crashing every 20 minutes for
anybody else and if that's the case you should open bugs so the issues
are fixed rather than adding useless comments
I was not trolling and I'm surprised by your reaction, Sebastien. I was
merely suggesting an alternative until Gnome gets fixed. And I have
filed bugs for all the problems I'm having. Reading blogs on the
subject, there are several people having problems with Nautilus
crashing. Some of those
your comments have nothing to do with this bug, are not useful and not
accurate, the GNOME in hardy is not buggier than previous versions,
there is some known pulseaudio (which is not a GNOME component) and gvfs
samba issues but not a lot of crashers and no performances issues. those
people who
[offtopic] I must say Gnome was every times quite good and stable... in
development versions too!
The only issues i have with hardy is this Bug and this Bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-print/+bug/223776, which
is why i've downgraded.
The only i wish is that bugs are fixed
I've Downgraded to Gutsy. (Because there are too many Bugs in Hardy)
This bug affects Gutsy too!
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
It's funny you say that frago. All those bugs that make Hardy the
buggiest release yet are all Gnome bugs. I switched to KDE about a month
ago and haven't had a problem. No PulseAudio screwing up audio, no gvfs
screwing up the networking connections, no crashing of Nautilus every 20
minutes.
And
When I quit Pulse audio some sounds work so I think the main problem is
the implantation of Pulse audio within Ubuntu 8.04.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Just to note. This issue also effects the firefox plugin.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Changed in: pulseaudio (Ubuntu)
Status: New = Confirmed
** Changed in: pulseaudio (Ubuntu Hardy)
Status: New = Confirmed
** Changed in: totem (Ubuntu)
Status: Invalid = Confirmed
** Changed in: totem (Ubuntu Hardy)
Status: Invalid = Confirmed
--
Failed to
Please everyone report if your using the amd64 version.
That's the version that gave me problems innitialy.
Now I'm using ubuntu i386 and I don't experience any problems.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification
I am using the i386 version. Still got issues.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Sheduled for 2008-07-01 (8.04.1)? Is an joke or not?! Whats about an
Hotfix Package? LT_S(upport!?)_ ...Pulseaudio is a essential part of
the Soundsystem and many low level users don't know how to switch to
ALSA! When you want to provide Pulseaudio as Feature you have to keep it
running.
Actually, two months is pretty speedy for them. There are bugs that are
several years old they have yet to fix.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Besides, I think they only release security fixes and other show stopper
fixes until their next maintenance release (8.04.1). Since there is a
workaround and audio really isn't a huge concern anyways (for servers),
they don't see this as a show stopper.
--
Failed to connect stream: Invalid
some days ago there was an kernel update! Can it be something with snd-
hda-intel???
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Same here! (Intel HDA ICH6)
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I second that...
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
This bug is quite persistant on my core2duo laptop (or at least a
similar bug) it even messed up lindvd.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
I think we should raise the severity of this bug. Ricardo Jorge?
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Pulseaudio is trippin here too!
once i switch to alsa, Totem will play. strange as it is...
vlc and some others already play with ease, only totem is having
problems...
looks like pulseaudio doesnt like the multiouts on my delta44, seems
like it prefers consumer audio interfaces with surround
** Changed in: pulseaudio (Ubuntu Hardy)
Target: None = ubuntu-8.04.1
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
mplayer does it too. But it will play the video with some work. Totem
just flat out errors out.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I am still having issues with this. Have the lastest kernel, 2.6.24-17
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Strangely enough, the machine I don't see this problem was updated to
kernel 2.6.24-17 and the one I hit this issue (using snd-hda-intel),
doesn't get 2.6.24-17, just stopped at 2.6.24-16.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug
Sorry about my inactivity, but I was not able to comment in the past weeks.
For what I see, maybe the issue has been corrected in a Linux kernel update.
Probably, I will download the x64 ubuntu version and test everything with the
latest updates.
If the problem occurs, I will notify you.
I thank
For my system, the problem has been cured by the recent update to the kernel: I
am now running
Linux ubuntu 2.6.24-17-rt #1 SMP PREEMPT RT Thu May 1 16:23:33 UTC 2008 i686
GNU/Linux
and the sound device (VIA 8237) is now correctly recognised and both ALSA and
pulseAudio servers generate sound.
I'm having similar problems with Hardy Heron.
Gutsy Gibbon was ok for sound, but I get nothing having upgraded.
Appears to be a failure to recognise my on-board sound device.
I've packaged together output of files recommended by
DebuggingSoundDevices page.
** Attachment added:
Hi all,
For those having the same symptoms than I have : module-alsa-sink.c:
Failed to create sink object I found a solution to make pulseaudio
working.
The problem was caused by a bad detection of my exotic sound card
(Terratec DMX 6Fire).
I modified the /etc/pulse/default.pa file to manually
Hello, For me in the sound playback preferences only OSS works properly,
all the others fail (including auto-detect). However, once I killed
pulseaudio (with killall pulseaudio), both auto-detect and OSS work
(the others still don't work).
here's some output from my /var/log/syslog
[EMAIL
I got alsa to work by deleting .asoundrc and .asoundrc.asoundconf from
my home directory
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Yes, changing the sound playback to alsa under SOUND will work!
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Same here confirmed. killing pulseaudio solves the problem
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
another confirmation that killing pulseaudio allows sound again
8.04 workstation upgraded from 7.10 (and previously upgraded from 7.04)
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
apologies for following up on my own post, but one more note...
I run a radio thru the line in on this box and that was functioning the
entire time. Dunno if that's relevant or not, but thought it
noteworthy.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
I'm experiencing the problem to. I think killing pulseaudio just force
Gnome to switch to ALSA :\
The sound is working fine before logging in (but at this time pulseaudio is not
running yet, so I guess this sound is played with ALSA, correct ?).
After logging in in Gnome, trying to play a
CORRECTION: I actually got it to work with PulseAudio! Instead of
switching to ALSA, I actually just did killall pulseaudio and the
sound started to work! I'm not sure if that works for everyone though.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You
Here also, I just killed PulseAudio and everything went fine.
So, this seems that we just have a workaround until now, right?
PS: If you' re using pidgin and kill pulseaudio, gaim will hog 100% of
your CPU, and will crash.
--
Failed to connect stream: Invalid argument
Confirming this bug and that switching to ALSA works.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I have this bug as well, however, switching to ALSA does not work for
me. I get the test sound and all of the system sounds play, even when
PulseAudio is selected. But the second I use Rhythmbox or Totem I get
the error.
--
Failed to connect stream: Invalid argument
I have the same problem. Have Ubuntu Hardy. PulseAudio in
System-Preferences-Sound returns: Failed to connect stream: Invalid
argument (autodetection also returns this problem). I must use Alsa - it works
good.
(Have SB AWE64 on ISA). pulseaudio -vv output attached.
** Attachment added:
Having same issues. Upgraded from 7.10 to 8.04 LTS. Autodetect was
selected. No sounds would play. Changed to ALSA and sounds play. If
using any sound device other than ALSA, get the following error:
audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample !
gconfaudiosink
Hi everyone,
Daniel, I tried your steps
1a)
$ lspci -nv|grep -A1 040[13]
00:1b.0 0403: 8086:293e (rev 02)
Subsystem: 1043:829f
1b) don't know what you mean :$
2a) did not work
2b) did work!!
my outputs are in the attachment (including the pulseaudio -vv command)
Many thanks!
**
I had the same issue and I found out that my audio device (and my eth0
too) works great when acpi is enabled (it's enabled by default, but i
had to change it for another reason). I hope this Information is useful
for you.
--
Failed to connect stream: Invalid argument
Alvin, please run 'pkill pulseaudio' before 'pulseaudio -vv' and send
this output, as requested by Daniel.
Ricardo, can you please also provide the debugging information requested
by Luke and Daniel?
** Changed in: pulseaudio (Ubuntu Hardy)
Target: ubuntu-8.04 = None
--
Failed to
I am having this same issue... what I noticed is that I boot with the
vmlinuz-2.6.24-16-386 kernel I get the error. If I boot with
vmlinuz-2.6.24-15-386 I don't get the error.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification
Bug confirmed on Hardy RC.
[EMAIL PROTECTED]:~$ pulseaudio -vv
I: main.c: Called SUID root and real-time/high-priority scheduling was
requested in the configuration. However, we lack the necessary priviliges:
I: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us
priviliges.
Definitely PulseAudio and/or ALSA, not Totem.
I'll add to Luke's suggestions for easier debugging:
1) The specific two items of import from alsa-info.sh output are a) `lspci
-nv|grep -A1 040[13]', and b) the AC'97 or HDA codec spew. If you have
firewire or usb audio, things are less trivial.
Hi everyone
I hope this helps, but updates are very important. When I downloaded and
installed Hardy Beta, PulseAudio didn't work on my laptop, with audio
issues and volume control issues. These have all been fixed in the weeks
following. So, can I suggest that you install all updates (incl the
My sound was working fine in Hardy with all daily update _until_ 2-3
days ago, when I ran into this problem.
(Sorry :-( )
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
From the description, there is nothing specific to totem in this bug; it
appears to be a general problem with sound playback through pulseaudio.
Luke, would you be able to take a look at this to triage it further?
Maimon,
This bug by now appears to include several different symptoms, not all
of
Hi,
On Wed, 2008-04-16 at 03:30 +, Steve Langasek wrote:
From the description, there is nothing specific to totem in this bug; it
appears to be a general problem with sound playback through pulseaudio.
Luke, would you be able to take a look at this to triage it further?
I'm obviously
Could everybody who is having issues please do the following:
1. Read https://wiki.ubuntu.com/DebuggingSoundProblems under the collecting
sound info section. There is a script you can download that will get all
necessary information about your sound hardware.
2. Please try and play audio through
Is everyone here using the x64 version? Because it only happened to me
initially when I was using the x64 version.
Try with the x32 version, this may be an x64-only bug.
In the latest alphas and betas, I've been using only the x32 version because It
solves this bug with me.
Try to do the same to
I got here due to a duplicate while running x32, but now sound is
running smooth afaik
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I'm getting this as well on a dell inspiron 1420. Video playback worked
properly a month or two ago, so it's been updates since then that broke
it.
I suspect the commenters on this bug are seeing at least two separate
bugs. One where shifting to a different sound system makes it work
(although
Same problem for me, I had to change for ALSA to make it work. If I want to use
PulseAudio, I have the same message :
Failed to connect stream: Invalid argument
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you
I have the same problem in Hardy Beta. I can't play any avi or mpeg movie (it
has worked before).
In /var/log/messages I get this:
Mar 30 17:01:43 ubuntu pulseaudio[5805]: sink-input.c: Failed to create sink
input: too many inputs per sink.
Kernel: Linux ubuntu 2.6.24-12-generic #1 SMP Wed Mar
** Changed in: totem (Ubuntu)
Status: Incomplete = New
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
It may be a hw detection issue. I had the same problem when using Hardy
Alpha 5, but not anymore with the recent updates of totem-gstreamer.
Please, give details on your hardware accordingly to
https://wiki.ubuntu.com/DebuggingSoundProblems
I managed to solve this by adding:
options
And this one is the result of pulseaudio -vv
** Attachment added: pulse.log
http://launchpadlibrarian.net/12505875/pulse.log
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop
Some attachments from an attempt to debug with crimsun in #ubuntu+1
This one is output of some commands run at his request.
** Attachment added: pulse.txt
http://launchpadlibrarian.net/12505874/pulse.txt
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
sound-properties-Message: Error running pipeline 'audiotestsrc wave=sine
freq=512 ! audioconvert ! audioresample ! gconfaudiosink': Failed to
connect stream: Invalid argument [pulsesink.c(411):
gst_pulsesink_prepare ():
/pipeline0/gconfaudiosink0/bin0/autoaudiosink0/autoaudiosink0-actual-
Ran into this one too. Switching to ALSA did work.
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
The same on my box.
Linux silex 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 GNU/Linux
I changed the sound preferences to ALSA under System/Preferences/Sound.
it works.
The hardware is not configured properly. Autodetection doesn't work.
--
Failed to connect stream: Invalid
Same issue here.
Linux linovski-laptop 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686
GNU/Linux
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
User.log in the system records reports some problems with PulseAudio
or something like that
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Managed to play with Totem changing the system sound to Conexant ANALOG - very
bad quality
I tried also Conexant Digital - But I was not able to hear anything
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are
I think this is more likely an hardware error
So I did an Hardware Database check and sent it to Ubuntu Hdw Database
Submission Id:
2d833f2c2a417ff5657ccd7ad1233694
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because
Already did
** Changed in: totem (Ubuntu)
Status: Incomplete = New
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
This is the error in the :
-First file:
** Message: Error: Failed to connect stream: Invalid argument
pulsesink.c(411): gst_pulsesink_prepare ():
/play/visbin/abin/audiosinkbin/audio-sink/bin6/autoaudiosink1/autoaudiosink1-actual-sink-pulse
-Second file:
0:00:13.597582229 20869 0x6635d0 INFO
Sent 2 reports :
first one is for totem --debug totem.txt
second is for GST_DEBUG_NO_COLOR=1 GST_DEBUG=3 totem --debug totem.txt
Thank you in advance
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member
GST_DEBUG_NO_COLOR=1 GST_DEBUG=3 totem --debug totem.txt
** Attachment added: totem.txt
http://launchpadlibrarian.net/11874893/totem.txt
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
totem --debug totem.txt
** Attachment added: totem.txt
http://launchpadlibrarian.net/11874758/totem.txt
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Managed to play with Totem going to the Sound ( System - Preferences - Sound
) and changing the system sound to ALSA.
But it sounds AWFULLY, sounds really bad
--
Failed to connect stream: Invalid argument
https://bugs.launchpad.net/bugs/191027
You received this bug notification because you
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/11872886/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/11872887/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/11872888/ProcStatus.txt
** Description
Thanks for your report, May you please run totem from the command line
as: GST_DEBUG_NO_COLOR=1 GST_DEBUG=3 totem --debug totem.txt and
attach that log to the report? thanks in advance.
** Changed in: totem (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
** Description changed:
Binary package hint: totem
I am unable to play any type of content in Totem,
and, the opening melodie (when the computers starts) sounds awfully...
I'm using the latest alpha development version of Hardy...
+ Update1: I'm also having trouble within Rythmbox, so
101 - 180 of 180 matches
Mail list logo
