GNOME Bugzilla – Bug 413552
crash in IP Telephony, VoIP and Video Conferencing: Making a call
Last modified: 2008-04-15 14:03:28 UTC
Version: 2.0.5 What were you doing when the application crashed? Making a call Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 102789120 vsize: 0 resident: 102789120 share: 0 rss: 25571328 rss_rlim: 0 CPU usage: start_time: 1172774243 rtime: 0 utime: 288 stime: 0 cutime:246 cstime: 0 timeout: 42 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208390816 (LWP 7231)] [New Thread -1252828272 (LWP 7273)] [New Thread -1264591984 (LWP 7272)] [New Thread -1264325744 (LWP 7270)] [New Thread -1253094512 (LWP 7269)] [New Thread -1252562032 (LWP 7256)] [New Thread -1252295792 (LWP 7255)] [New Thread -1252029552 (LWP 7252)] [New Thread -1241539696 (LWP 7245)] [New Thread -1211679856 (LWP 7238)] [New Thread -1211413616 (LWP 7237)] 0x0045e402 in __kernel_vsyscall ()
+ Trace 114981
Thread 10 (Thread -1211679856 (LWP 7238))
----------- .xsession-errors --------------------- ** (bug-buddy:7275): WARNING **: Couldn't load icon for Theme ** (bug-buddy:7275): WARNING **: Couldn't load icon for Windows ** (bug-buddy:7275): WARNING **: Couldn't load icon for Show Desktop Could not find the frame base for "PSyncPoint::Wait(PTimeInterval const&)". Could not find the frame base for "PTimerList::Process()". Could not find the frame base for "PThread::PXBlockOnIO(int, int, PTimeInterval const&)". Could not find the frame base for "PSocket::Select(PSocket::SelectList&, PSocket::SelectList&, PSocket::SelectList&, PTimeInterval const&)". Could not find the frame base for "PThread::PXBlockOnIO(int, int, PTimeInterval const&)". Could not find the frame base for "PThread::PXBlockOnIO(int, int, PTimeInterval const&)". Could not find the frame base for "PThread::PXBlockOnIO(int, int, PTimeInterval const&)". Could not find the frame base for "PSimpleThread::Main()". Could not find the frame base for "PThread::PX_ThreadStart(void*)". --------------------------------------------------
Hmmm... crash in libasound2... can you reproduce it ?
It reproduces it self, can't figure out exactly what's going on here, tried starting ekiga from console to get output, does this help? "ekiga: pcm_params.c:2351: sndrv_pcm_hw_params: Assertion `err >= 0' failed. Xlib: unexpected async reply (sequence 0xea1ec)!" Just a stab in the dark, could this be prelink-related?
Eh... the first error message says libasound2 has had a problem. The second means we have a threading issue. The relation between the two is not obvious :-/
The first message indicates a bug in libasound. The second message is a conclusion of the crash triggered by this bug in libasound. Try this : arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 16000 -f S16_LE - and this : arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 8000 -f S16_LE - and this : arecord -D default -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 16000 -f S16_LE - and this : arecord -D default -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 8000 -f S16_LE - Do you have the same problem ?
(In reply to comment #4) > The first message indicates a bug in libasound. > The second message is a conclusion of the crash triggered by this bug in > libasound. > > Try this : > arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c > 1 -r 16000 -f S16_LE - [dado@amelie ~]$ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 16000 -f S16_LE - Recording WAVE '-' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono underrun!!! (at least 26321,785 ms long) Aborted by signal Interrupt... Aborted by signal Interrupt... > and this : > arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c > 1 -r 8000 -f S16_LE - [dado@amelie ~]$ arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 8000 -f S16_LE - Recording WAVE '-' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono underrun!!! (at least 30929,183 ms long) Aborted by signal Interrupt... Aborted by signal Interrupt... > and this : > arecord -D default -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c > 1 -r 16000 -f S16_LE - [dado@amelie ~]$ arecord -D default -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 16000 -f S16_LE - Recording WAVE '-' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono underrun!!! (at least 31965,413 ms long) Aborted by signal Interrupt... Aborted by signal Interrupt... > and this : > arecord -D default -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c > 1 -r 8000 -f S16_LE - [dado@amelie ~]$ arecord -D default -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 8000 -f S16_LE - Recording WAVE '-' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono underrun!!! (at least 23659,793 ms long) Aborted by signal Interrupt... Aborted by signal Interrupt... > Do you have the same problem ? If the "underrun!!" isn't the same problem, then no. I'm not sure how long should I let it run, I guessed a minute would be OK. Anyway, I've noticed that it always crashes the first time (when calling a 2.0.2 user), it's 60-40 that it'll crash the second time and the third time it usually works. The crashes started after an upgrade to 2.0.5 (2.0.2 never crashed). FC has an ekiga-debuginfo package, if I install it and send the crash info (how to do that?), would that help any?
That wouldn't hurt, but I checked our alsa code just in case : we do check correctly for error each time we play with snd_pcm_hw_params... so it really looks like this bug is NOTGNOME.
(In reply to comment #6) > That wouldn't hurt, but I checked our alsa code just in case : we do check > correctly for error each time we play with snd_pcm_hw_params... so it really > looks like this bug is NOTGNOME. > OK, if you say so. Just in case, here's my yum upgrade list (first day is when ekiga upgraded and started crashing), maybe some other package is causing the problem? Feb 21 22:24:34 Updated: php-common.i386 5.1.6-3.4.fc6 Feb 21 22:25:16 Updated: pwlib.i386 1.10.4-1.fc6 Feb 21 22:25:52 Updated: opal.i386 2.2.5-1.fc6 Feb 21 22:26:18 Updated: audit-libs.i386 1.4.1-1.fc6 Feb 21 22:26:18 Updated: php-pdo.i386 5.1.6-3.4.fc6 Feb 21 22:26:21 Updated: php-cli.i386 5.1.6-3.4.fc6 Feb 21 22:26:22 Updated: php.i386 5.1.6-3.4.fc6 Feb 21 22:27:55 Updated: amarok.i386 1.4.5-4.fc6 Feb 21 22:28:06 Updated: selinux-policy.noarch 2.4.6-40.fc6 Feb 21 22:28:13 Updated: spamassassin.i386 3.1.8-2.fc6 Feb 21 22:28:17 Updated: php-devel.i386 5.1.6-3.4.fc6 Feb 21 22:28:18 Updated: smolt.noarch 0.9-1.fc6 Feb 21 22:28:19 Updated: audit-libs-python.i386 1.4.1-1.fc6 Feb 21 22:28:20 Updated: php-mbstring.i386 5.1.6-3.4.fc6 Feb 21 22:28:22 Updated: php-mysql.i386 5.1.6-3.4.fc6 Feb 21 22:28:23 Updated: yum-utils.noarch 1.0.3-1.fc6 Feb 21 22:28:25 Updated: xterm.i386 224-1.fc6 Feb 21 22:29:12 Updated: ekiga.i386 2.0.5-2.fc6 Feb 21 22:29:12 Updated: yum-fastestmirror.noarch 1.0.3-1.fc6 Feb 21 22:29:13 Updated: php-gd.i386 5.1.6-3.4.fc6 Feb 21 22:29:14 Updated: php-xml.i386 5.1.6-3.4.fc6 Feb 21 22:29:46 Updated: selinux-policy-targeted.noarch 2.4.6-40.fc6 Feb 21 22:29:47 Updated: yum-versionlock.noarch 1.0.3-1.fc6 Feb 23 17:39:47 Updated: fuse-libs.i386 2.6.3-2.fc6 Feb 23 17:39:49 Updated: fuse.i386 2.6.3-2.fc6 Feb 23 17:39:53 Updated: ntfs-3g.i386 2:1.0-1.fc6 Feb 23 17:40:01 Updated: pam.i386 0.99.6.2-3.16.fc6 Feb 23 17:40:02 Installed: lucene-devel.i386 1.4.3-1jpp.14 Feb 23 17:40:03 Updated: slang.i386 2.0.7-1.fc6 Feb 23 17:40:04 Updated: beryl-settings-simple.i386 0.1.9999.2-1.fc6 Feb 23 17:41:21 Updated: eclipse-platform.i386 1:3.2.2-1.fc6 Feb 23 17:41:43 Updated: eclipse-rcp.i386 1:3.2.2-1.fc6 Feb 23 17:41:53 Updated: eclipse-ecj.i386 1:3.2.2-1.fc6 Feb 23 17:42:04 Installed: kmod-fglrx.i686 8.34.8-1.2.6.19_1.2911.fc6 Feb 23 17:43:03 Updated: xorg-x11-drv-fglrx.i386 8.34.8-3.lvn6 Feb 23 17:43:06 Updated: beryl-core.i386 0.1.9999.2-1.fc6 Feb 23 17:43:15 Updated: emerald.i386 0.1.9999.2-1.fc6 Feb 23 17:43:22 Updated: beryl-plugins.i386 0.1.9999.2-1.fc6 Feb 23 17:43:30 Updated: beryl-settings.i386 0.1.9999.2-1.fc6 Feb 23 17:43:48 Updated: emerald-themes.noarch 0.1.9999.2-1.fc6 Feb 23 17:44:05 Updated: beryl-manager.i386 0.1.9999.2-1.fc6 Feb 23 17:44:07 Updated: heliodor.i386 0.1.9999.2-1.fc6 Feb 23 17:44:15 Updated: aquamarine.i386 0.1.9999.2-2.fc6 Feb 23 17:44:16 Updated: bdock.i386 0.1.9999.2-1.fc6 Feb 23 17:44:27 Updated: libswt3-gtk2.i386 1:3.2.2-1.fc6 Feb 23 17:44:27 Updated: beryl-kde.i386 0.1.9999.2-1.fc6 Feb 23 17:44:27 Updated: beryl-gnome.i386 0.1.9999.2-1.fc6 Feb 23 17:44:29 Updated: beryl-core-devel.i386 0.1.9999.2-1.fc6 Feb 23 17:44:33 Updated: emerald-devel.i386 0.1.9999.2-1.fc6 Feb 23 17:44:33 Updated: beryl.i386 0.1.9999.2-1.fc6 Feb 24 18:41:08 Updated: kdemultimedia-extras-nonfree.i386 3.5.6-3.lvn6 Feb 24 18:41:11 Updated: at.i386 3.1.8-85.fc6 Feb 24 18:41:12 Updated: pinfo.i386 0.6.9-3.fc6 Feb 27 13:56:28 Updated: nspr.i386 4.6.5-0.6.0.fc6 Feb 27 13:56:32 Updated: nss.i386 3.11.5-0.6.0.fc6 Feb 27 13:56:34 Updated: audit-libs.i386 1.4.2-2.fc6 Feb 27 13:57:52 Updated: xorg-x11-drv-fglrx.i386 8.34.8-5.lvn6 Feb 27 13:58:18 Updated: beryl-core.i386 0.1.9999.2-2.fc6 Feb 27 13:58:22 Updated: beryl-plugins.i386 0.1.9999.2-2.fc6 Feb 27 13:58:22 Updated: beryl-kde.i386 0.1.9999.2-2.fc6 Feb 27 13:58:22 Updated: beryl-gnome.i386 0.1.9999.2-2.fc6 Feb 27 13:58:44 Updated: bind-libs.i386 31:9.3.4-3.fc6 Feb 27 13:58:45 Updated: crontabs.noarch 1.10-12.fc6 Feb 27 13:58:47 Updated: nss-tools.i386 3.11.5-0.6.0.fc6 Feb 27 13:58:48 Updated: perl-Cairo.i386 1.023-1.fc6 Feb 27 13:58:48 Updated: beryl.i386 0.1.9999.2-2.fc6 Feb 27 13:58:50 Updated: dvdauthor.i386 0.6.14-1.fc6 Feb 27 13:59:12 Updated: tzdata.noarch 2007c-1.fc6 Feb 27 13:59:14 Updated: beryl-core-devel.i386 0.1.9999.2-2.fc6 Feb 27 13:59:15 Updated: audit-libs-python.i386 1.4.2-2.fc6 Feb 28 13:05:41 Updated: gnome-python2-extras.i386 2.14.2-9.fc6 Feb 28 13:05:46 Updated: xorg-x11-server-Xorg.i386 1.1.1-47.6.fc6 Feb 28 13:05:48 Updated: vixie-cron.i386 4:4.1-68.fc6 Feb 28 13:05:48 Updated: gnome-python2-libegg.i386 2.14.2-9.fc6 Feb 28 22:48:11 Installed: gdb.i386 6.5-15.fc6 Feb 28 22:49:34 Installed: bug-buddy.i386 1:2.16.0-4.fc6 Mar 01 14:04:43 Updated: xorg-x11-drv-fglrx.i386 8.34.8-7.lvn6 Mar 01 14:05:05 Updated: xmoto.i386 0.2.4-1.fc6 Mar 01 14:26:38 Installed: cyrus-sasl-devel.i386 2.1.22-4
The underrun is not normal though...
*** Bug 414038 has been marked as a duplicate of this bug. ***
*** Bug 419102 has been marked as a duplicate of this bug. ***
*** Bug 419162 has been marked as a duplicate of this bug. ***
Just wanted to point out that crashed were pretty frequent when making a call to a 2.0.2 user (once 10 in a row), but when that other user upgraded to 2.0.5 (same distro, so same build as me), now I get one or no crashes a call (the other user gets no crashed at all). We use same packages, same kernels, but different soundcards equals different sound drivers, I use snd_ens1371, could that be the error source? Maybe it could help, maybe not, thought you should know.
*** Bug 422067 has been marked as a duplicate of this bug. ***
*** Bug 424827 has been marked as a duplicate of this bug. ***
*** Bug 431699 has been marked as a duplicate of this bug. ***
*** Bug 432732 has been marked as a duplicate of this bug. ***
*** Bug 434347 has been marked as a duplicate of this bug. ***
Reports come in regularly, but we still haven't been able to pinpoint the issue exactly. I'm very tempted to close it as NOTGNOME...
I'll close it as NOTGNOME if we don't get more reports soon (say, two weeks).
(In reply to comment #19) > I'll close it as NOTGNOME if we don't get more reports soon (say, two weeks). > Good enough for me, I've been using Twinkle for two months now and must say (NHF anyone) that it runs much better on my machine. Ekiga tends to burn up to 50% for Speex encoding/decoding (video disabled) while Twinkle uses about 10% tops, sound quality seems the same (same codec), not to say it doesn't crash. :) This is NOT a flamebait.
Eh, if it works better for you, it's nice. Notice though that just "speex" doesn't mean much... there are several speex settings : if you use one with high quality on one side and one low quality on the other side, the load won't be the same. And the resulting sound quality may still be the same, if the original audio source isn't of wonderful quality...
*** Bug 447764 has been marked as a duplicate of this bug. ***
*** Bug 448983 has been marked as a duplicate of this bug. ***
*** Bug 449245 has been marked as a duplicate of this bug. ***
*** Bug 449337 has been marked as a duplicate of this bug. ***
*** Bug 449608 has been marked as a duplicate of this bug. ***
*** Bug 454161 has been marked as a duplicate of this bug. ***
*** Bug 454727 has been marked as a duplicate of this bug. ***
*** Bug 458440 has been marked as a duplicate of this bug. ***
*** Bug 459657 has been marked as a duplicate of this bug. ***
*** Bug 469338 has been marked as a duplicate of this bug. ***
*** Bug 469908 has been marked as a duplicate of this bug. ***
*** Bug 470825 has been marked as a duplicate of this bug. ***
*** Bug 471999 has been marked as a duplicate of this bug. ***
"ekiga: pcm_params.c:2351: sndrv_pcm_hw_params: Assertion `err >= 0' failed. It is an ALSA bug! See : http://www.pulseaudio.org/ticket/23 and https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 It seems upgrading ALSA fixes the problem.
*** Bug 479589 has been marked as a duplicate of this bug. ***
*** Bug 482932 has been marked as a duplicate of this bug. ***
*** Bug 484546 has been marked as a duplicate of this bug. ***
*** Bug 487359 has been marked as a duplicate of this bug. ***
*** Bug 487754 has been marked as a duplicate of this bug. ***
*** Bug 489002 has been marked as a duplicate of this bug. ***
*** Bug 481906 has been marked as a duplicate of this bug. ***
*** Bug 494384 has been marked as a duplicate of this bug. ***
*** Bug 494595 has been marked as a duplicate of this bug. ***
*** Bug 495126 has been marked as a duplicate of this bug. ***
*** Bug 495404 has been marked as a duplicate of this bug. ***
*** Bug 497838 has been marked as a duplicate of this bug. ***
*** Bug 501131 has been marked as a duplicate of this bug. ***
*** Bug 501367 has been marked as a duplicate of this bug. ***
*** Bug 501639 has been marked as a duplicate of this bug. ***
*** Bug 506091 has been marked as a duplicate of this bug. ***
*** Bug 506223 has been marked as a duplicate of this bug. ***
*** Bug 507839 has been marked as a duplicate of this bug. ***
*** Bug 507951 has been marked as a duplicate of this bug. ***
*** Bug 517007 has been marked as a duplicate of this bug. ***
*** Bug 508154 has been marked as a duplicate of this bug. ***
*** Bug 509014 has been marked as a duplicate of this bug. ***
*** Bug 515129 has been marked as a duplicate of this bug. ***
See this bug report : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3825
Please also see : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2601 It would be nice if people with that bug could comment on the ALSA bug tracker and help fixing the problem...
*** Bug 506184 has been marked as a duplicate of this bug. ***
*** Bug 520630 has been marked as a duplicate of this bug. ***
See also : https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3825 The PulseAudio bug is fixed by the patches provided in bug report with ID 2601. But people not using PulseAudio can also have the problem.
*** Bug 528106 has been marked as a duplicate of this bug. ***
*** Bug 528115 has been marked as a duplicate of this bug. ***
*** Bug 528119 has been marked as a duplicate of this bug. ***
"The PulseAudio bug is fixed by the patches provided in bug report with ID 2601. But people not using PulseAudio can also have the problem." I'm using PulseAudio and have the same problem (last 3 bug reports must be mine). "It would be nice if people with that bug could comment on the ALSA bug tracker and help fixing the problem..." I'd love to do that. What should I comment exactly? Do you have any ideas about the infos I should provide?