Bug 413209 – crash in Ekiga Softphone: yep, reproducable! see b...

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 413209 - crash in Ekiga Softphone: yep, reproducable! see b...


Summary:	crash in Ekiga Softphone: yep, reproducable! see b...


Status:	RESOLVED DUPLICATE of bug 364480

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:	2007-02-28 20:43 UTC by Florian
Modified:	2007-02-28 20:50 UTC

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

Description Florian 2007-02-28 20:43:29 UTC

Version: 2.0.3

What were you doing when the application crashed?
yep,
reproducable!
see bug #412408
Haven't tried it with 2.0.5.
I will have a look where to get it.



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

Memory status: size: 125599744 vsize: 0 resident: 125599744 share: 0 rss: 28209152 rss_rlim: 0
CPU usage: start_time: 1172694877 rtime: 0 utime: 1158 stime: 0 cutime:1089 cstime: 0 timeout: 69 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 -1247660368 (LWP 6364)]
[New Thread -1317094496 (LWP 6587)]
[New Thread -1316320352 (LWP 6586)]
[New Thread -1342805088 (LWP 6533)]
[New Thread -1342538848 (LWP 6532)]
[New Thread -1342272608 (LWP 6531)]
[New Thread -1341408352 (LWP 6529)]
[New Thread -1333015648 (LWP 6527)]
[New Thread -1250047072 (LWP 6515)]
[New Thread -1249780832 (LWP 6514)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 114726

Thread 9 (Thread -1250047072 (LWP 6515))

#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 PTime::operator-
from /usr/lib/libpt.so.1.10.2
#5 PIPCacheData::HasAged
from /usr/lib/libpt.so.1.10.2
#6 PHostByName::GetHost
from /usr/lib/libpt.so.1.10.2
#7 PHostByName::GetHostAddress
from /usr/lib/libpt.so.1.10.2
#8 PIPSocket::GetHostAddress
from /usr/lib/libpt.so.1.10.2
#9 OpalInternalIPTransport::GetIpAndPort
from /usr/lib/libopal.so.2.2
#10 ??
#11 ??
#12 ??
#13 PString::operator==
from /usr/lib/libpt.so.1.10.2
#14 OpalTransportAddress::GetIpAndPort
from /usr/lib/libopal.so.2.2
#15 Opal_YUV420P_H261_CIF
from /usr/lib/libopal.so.2.2
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 OpalTransportIP::SetRemoteAddress
from /usr/lib/libopal.so.2.2
#23 ??
#24 ??
#25 ??
#26 ??
from /usr/lib/libopal.so.2.2
#27 ??
#28 OpalTransportUDP::ReadPDU
from /usr/lib/libopal.so.2.2

Comment 1 Christian Kirbach 2007-02-28 20:50:11 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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