GNOME Bugzilla – Bug 134007
[alsasink] assertion failure in alsalib snd_pcm_plug_hw_params()
Last modified: 2004-12-22 21:47:04 UTC
I just installed gstreamer 0.7.4 and recompiled rhythmbox 0.7.0 against it. I had gstreamer 0.6.4 previously working fine with rhythmbox 0.6.x using ALSA. After the upgrade, I got the following error : rhythmbox: pcm_plug.c:882: snd_pcm_plug_hw_params: Assertion `err >= 0' failed. Program received signal SIGABRT, Aborted. With this backtrace : (gdb) bt
+ Trace 44007
Changing the 'alsasink' I had in my GConf key to 'alsasink device="hw:0"' fixes the problem, but it would be really better to have ALSA support working by default, and in all cases, I doubt any error of this kind should generate a segfault. This is using the latest Fedora Core Development 2.6 kernel and ALSA 1.0.2 userland tools from freshrpms.net. I now also have another problem with rhythmbox which is that when arriving near the end of the song currently being played, the playback simply stops a few seconds before the end of the song and it never goes to the next. As this is both with a new gstreamer and a new rhythmbox, I don't really know which is to blame, I'll have to look more into it.
This is a bug in alsalib. I am aware of this problem but I cannot fix it. You'll need to file a bug there.
how about making device=dev:hw0 the default for alsasink, because it's the most sensible one to use ?
I don't agree that it's sensible to not use the device explicitly marked as default. Especially because the "default" (aka "plughw:0") device is supposed to support weird soundcards by doing the mixing automatically. It's an alsalib bug plain and simple. I just fiogured out alsa got a bugtracker. Please see https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php? bug_id=0000116
*** Bug 136174 has been marked as a duplicate of this bug. ***
*** Bug 135422 has been marked as a duplicate of this bug. ***
*** Bug 136815 has been marked as a duplicate of this bug. ***
*** Bug 137891 has been marked as a duplicate of this bug. ***
*** Bug 137994 has been marked as a duplicate of this bug. ***
I have a soundcard that exhibits this problem and am willing to work with the alsa team on getting this resolved, however their bug tracking system seems broken so I can't sign up there. Trying to reach the admin via email...
Benjamin: I still can't sign up for an account on https://bugtrack.alsa-project.org/alsa-bug/ and get no response from webmaster@alsa-project.org Could you perhaps add a notice to the bug in question and perhaps it gets noticed. You are free to add my email address noa@resare.com.
*** Bug 140589 has been marked as a duplicate of this bug. ***
*** Bug 141984 has been marked as a duplicate of this bug. ***
*** Bug 137052 has been marked as a duplicate of this bug. ***
*** Bug 133778 has been marked as a duplicate of this bug. ***
Thanks to Zaheer Merali for providing me with an ssh account, so I was able to trace this bug. GStreamer now successfully works around this bug in alsa.
Hi Benjamin, This has apparently been fixed in CVS but glancing through http://freedesktop.org/cgi-bin/viewcvs.cgi/gstreamer/gstreamer/ChangeLog I could not find out when / where. Any chance you can ping this bug and or https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121671 when an official version of gstreamer (as opposed to a CVS) is released with this fixed?
The change you are interested in is http://freedesktop.org/cgi-bin/viewcvs.cgi/gstreamer/gst-plugins/ChangeLog?r1=1.755&r2=1.756 This will be fixed in the next version of gst-plugins (0.8.2) which should be out "soon"
*** Bug 147080 has been marked as a duplicate of this bug. ***
*** Bug 146485 has been marked as a duplicate of this bug. ***
*** Bug 143476 has been marked as a duplicate of this bug. ***
*** Bug 149432 has been marked as a duplicate of this bug. ***