Bug 372772 – crash in Ekiga Softphone: calling ekiga from OpenM...

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 372772 - crash in Ekiga Softphone: calling ekiga from OpenM...


Summary:	crash in Ekiga Softphone: calling ekiga from OpenM...


Status:	RESOLVED DUPLICATE of bug 361765

Product:	ekiga
Classification:	Applications
Component:	general
Version:	2.0.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Ekiga maintainers
QA Contact:	Ekiga maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-09 01:53 UTC by superkonduktor
Modified:	2006-11-10 08:53 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description superkonduktor 2006-11-09 01:53:35 UTC

Version: 2.0.3

What were you doing when the application crashed?
calling ekiga from OpenMCU h323


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

Memory status: size: 110669824 vsize: 0 resident: 110669824 share: 0 rss: 30158848 rss_rlim: 0
CPU usage: start_time: 1163081590 rtime: 0 utime: 575 stime: 0 cutime:255 cstime: 0 timeout: 320 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)
[Thread debugging using libthread_db enabled]
[New Thread -1246804304 (LWP 14283)]
[New Thread -1303250016 (LWP 14448)]
[New Thread -1300980832 (LWP 14447)]
[New Thread -1300182112 (LWP 14442)]
[New Thread -1298732128 (LWP 14441)]
[New Thread -1299915872 (LWP 14432)]
[New Thread -1297933408 (LWP 14406)]
[New Thread -1298465888 (LWP 14310)]
[New Thread -1298199648 (LWP 14309)]
[New Thread -1297278048 (LWP 14304)]
[New Thread -1305670752 (LWP 14298)]
[New Thread -1249018976 (LWP 14286)]
[New Thread -1248752736 (LWP 14285)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 84595

Thread 5 (Thread -1298732128 (LWP 14441))

#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 H323_RTPChannel::OnSendingPDU
from /usr/lib/libopal.so.2.2
#5 ??
#6 ??
#7 ??
#8 ??
from /usr/lib/libopal.so.2.2
#9 ??
#10 ??
#11 ??
#12 H323_RealTimeChannel::OnSendingPDU
from /usr/lib/libopal.so.2.2
#13 ??
#14 ??
#15 ??
#16 ??
from /usr/lib/libopal.so.2.2
#17 ??
#18 ??
#19 ??
#20 H323Connection::HandleFastStartAcknowledge
from /usr/lib/libopal.so.2.2
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??

Comment 1 Christian Kirbach 2006-11-10 00:38:19 UTC

crash in libopal

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Damien Sandras 2006-11-10 08:53:36 UTC

It is actually a DUP of #361765 (even if the bt is different).

We are waiting for 359655 to be confirmed as a gnome-vfs bug before releasing 2.0.4. 

*** This bug has been marked as a duplicate of 361765 ***