After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 361680 - crash in Ekiga Softphone: Placing a call with ekig...
crash in Ekiga Softphone: Placing a call with ekig...
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: High critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
: 367320 377756 380427 392838 394583 406139 409416 411957 413010 417176 417309 419127 419466 419855 420574 420902 424002 430349 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-12 11:36 UTC by Beni
Modified: 2007-04-16 16:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Debug output (ekiga -d 4) (164.16 KB, text/plain)
2006-10-12 19:34 UTC, Beni
Details

Description Beni 2006-10-12 11:36:44 UTC
Version: 2.0.3

What were you doing when the application crashed?
Placing a call with ekiga, just after the connection is made it exists with error: "Jitter thread did not terminate correclty".


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/ekiga'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Comment 1 Snark 2006-10-12 11:46:43 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Can you get us one with debugging
symbols? Please see http://live.gnome.org/GettingTraces for more information on
how to do so.

Can you reproduce this?

Comment 2 Beni 2006-10-12 11:57:43 UTC
(In reply to comment #1)
> Thanks for the bug report. Unfortunately, that stack trace is not very useful
> in determining the cause of the crash. Can you get us one with debugging
> symbols? Please see http://live.gnome.org/GettingTraces for more information on
> how to do so.
> 
> Can you reproduce this?
> 

Yes, I can reproduce it. It happens to me every time the call connects.

Better debug trace (I hope):

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 126484480 vsize: 0 resident: 126484480 share: 0 rss: 29814784 rss_rlim: 0
CPU usage: start_time: 1160653873 rtime: 0 utime: 616 stime: 0 cutime:554 cstime: 0 timeout: 62 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/ekiga'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1246991696 (LWP 7359)]
[New Thread -1325888608 (LWP 7519)]
[New Thread -1324508256 (LWP 7510)]
[New Thread -1325622368 (LWP 7399)]
[New Thread -1325184096 (LWP 7398)]
[New Thread -1324242016 (LWP 7383)]
[New Thread -1323975776 (LWP 7382)]
[New Thread -1323680864 (LWP 7378)]
[New Thread -1315288160 (LWP 7376)]
[New Thread -1249207392 (LWP 7367)]
[New Thread -1248941152 (LWP 7366)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1325888608 (LWP 7519))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __after_morecore_hook
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
  • #6 ??
  • #7 ??
    from /usr/lib/libopal.so.2.2
  • #8 ??
  • #9 ??
    from /usr/lib/libopal.so.2.2
  • #10 ??
  • #11 ??
    from /usr/lib/libopal.so.2.2
  • #12 OpalRTPMediaStream::WritePacket
    from /usr/lib/libopal.so.2.2
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 PAbstractList::GetReferenceAt
    from /usr/lib/libpt.so.1.10.2
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
    from /usr/lib/libopal.so.2.2
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 OpalMediaPatch::Sink::WriteFrame
    from /usr/lib/libopal.so.2.2
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
    from /usr/lib/libpt.so.1.10.2
  • #30 ??

Comment 3 Damien Sandras 2006-10-12 12:28:04 UTC
That's a kernel problem with your sound driver, not an Ekiga problem.

What plugin are you using for audio? ALSA?
Comment 4 Beni 2006-10-12 12:44:19 UTC
(In reply to comment #3)
> That's a kernel problem with your sound driver, not an Ekiga problem.
> 
> What plugin are you using for audio? ALSA?
> 

Good to hear it's not a problem with Ekiga, it used to work OK in Ubuntu Dapper. 

Yes, using ALSA.
Comment 5 Damien Sandras 2006-10-12 18:16:53 UTC
Does arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c
1 -r 8000 -f S16_LE - work?
Comment 6 Beni 2006-10-12 19:19:30 UTC
(In reply to comment #5)
> Does arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c
> 1 -r 8000 -f S16_LE - work?
> 

Yes, it works without any problems.
Comment 7 Damien Sandras 2006-10-12 19:25:37 UTC
OK, please post a -d 4 output.

(ekiga -d 4 > output.txt 2>&1)

"Jitter buffer thread did not terminate" means that Ekiga can not close the sound channel. Most of the time, it is due to a bug in the driver. It never happened with ALSA so far. It was happening with old OSS drivers. Notice also that the sound handling code has not changed between 2.0.x releases of Ekiga, so I would suspect a problem triggered by one of your updates.
Comment 8 Beni 2006-10-12 19:34:49 UTC
Created attachment 74593 [details]
Debug output (ekiga -d 4)
Comment 9 Damien Sandras 2006-10-12 19:40:29 UTC
Does it also happen when placing a SIP call?

Notice the "jitter buffer continuously full" messages.
Comment 10 Beni 2006-10-12 19:47:19 UTC
(In reply to comment #9)
> Does it also happen when placing a SIP call?
> 
> Notice the "jitter buffer continuously full" messages.
> 

No, SIP seems to be OK (called the Ekiga.net echo service)

Also, strange to me the line (almost the last line): "Han ocurrido múltiples errores de segmentación". ("There were multiple segmentation faults") (Translated from Spanish)
Comment 11 Snark 2006-10-12 19:59:36 UTC
Hmmm... even if the jitter buffer is always full, ekiga should handle it gracefully :-/
Comment 12 Damien Sandras 2006-10-28 16:54:05 UTC
A bug was introduced by myself when fixing SIP reinvite between 2.0.2 and 2.0.3. It is now fixed.
Comment 13 Beni 2006-10-28 18:03:59 UTC
(In reply to comment #12)
> A bug was introduced by myself when fixing SIP reinvite between 2.0.2 and
> 2.0.3. It is now fixed.
> 

Thanks, will test it when a release becomes available :)
Comment 14 Damien Sandras 2006-10-28 20:51:31 UTC
I'll release 2.0.4 as soon as bug #359655 is confirmed to be outside of Ekiga ;)
Comment 15 Damien Sandras 2006-10-30 08:23:44 UTC
*** Bug 367320 has been marked as a duplicate of this bug. ***
Comment 16 Damien Sandras 2006-11-21 19:43:52 UTC
*** Bug 377756 has been marked as a duplicate of this bug. ***
Comment 17 Damien Sandras 2006-11-29 10:13:15 UTC
*** Bug 380427 has been marked as a duplicate of this bug. ***
Comment 18 Snark 2006-11-29 20:42:17 UTC
*** Bug 380630 has been marked as a duplicate of this bug. ***
Comment 19 Damien Sandras 2007-01-04 21:21:09 UTC
*** Bug 392838 has been marked as a duplicate of this bug. ***
Comment 20 Damien Sandras 2007-01-09 11:55:31 UTC
*** Bug 394583 has been marked as a duplicate of this bug. ***
Comment 21 Snark 2007-01-10 06:06:02 UTC
*** Bug 394788 has been marked as a duplicate of this bug. ***
Comment 22 Snark 2007-01-10 06:06:11 UTC
*** Bug 394785 has been marked as a duplicate of this bug. ***
Comment 23 Damien Sandras 2007-02-10 11:32:24 UTC
*** Bug 406139 has been marked as a duplicate of this bug. ***
Comment 24 Damien Sandras 2007-02-19 09:36:09 UTC
*** Bug 409416 has been marked as a duplicate of this bug. ***
Comment 25 Damien Sandras 2007-02-26 09:07:44 UTC
*** Bug 411957 has been marked as a duplicate of this bug. ***
Comment 26 Damien Sandras 2007-02-28 10:39:28 UTC
*** Bug 413010 has been marked as a duplicate of this bug. ***
Comment 27 Damien Sandras 2007-03-11 20:11:51 UTC
*** Bug 417176 has been marked as a duplicate of this bug. ***
Comment 28 Snark 2007-03-12 06:55:14 UTC
*** Bug 417309 has been marked as a duplicate of this bug. ***
Comment 29 Snark 2007-03-17 05:22:29 UTC
*** Bug 419127 has been marked as a duplicate of this bug. ***
Comment 30 Snark 2007-03-17 19:40:25 UTC
*** Bug 419466 has been marked as a duplicate of this bug. ***
Comment 31 Damien Sandras 2007-03-18 19:37:03 UTC
*** Bug 419855 has been marked as a duplicate of this bug. ***
Comment 32 Damien Sandras 2007-03-20 18:43:58 UTC
*** Bug 420574 has been marked as a duplicate of this bug. ***
Comment 33 Damien Sandras 2007-03-21 09:00:44 UTC
*** Bug 420902 has been marked as a duplicate of this bug. ***
Comment 34 Damien Sandras 2007-03-29 07:40:34 UTC
*** Bug 424002 has been marked as a duplicate of this bug. ***
Comment 35 Snark 2007-04-16 16:46:40 UTC
*** Bug 430349 has been marked as a duplicate of this bug. ***