Bug 382028 – crash in Ekiga Softphone: estaba arrancando e inic...

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 382028 - crash in Ekiga Softphone: estaba arrancando e inic...


Summary:	crash in Ekiga Softphone: estaba arrancando e inic...


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:	2006-12-03 21:38 UTC by javi832
Modified:	2006-12-04 08:56 UTC

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

Description javi832 2006-12-03 21:38:39 UTC

Version: 2.0.3

What were you doing when the application crashed?
estaba arrancando e iniciando una sesion


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

Memory status: size: 98971648 vsize: 0 resident: 98971648 share: 0 rss: 27164672 rss_rlim: 0
CPU usage: start_time: 1165180718 rtime: 0 utime: 200 stime: 0 cutime:186 cstime: 0 timeout: 14 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 -1246845264 (LWP 4474)]
[New Thread -1297982560 (LWP 4632)]
[New Thread -1297716320 (LWP 4631)]
[New Thread -1297106016 (LWP 4618)]
[New Thread -1296839776 (LWP 4617)]
[New Thread -1296573536 (LWP 4616)]
[New Thread -1295627360 (LWP 4611)]
[New Thread -1287234656 (LWP 4608)]
[New Thread -1248400480 (LWP 4593)]
[New Thread -1248134240 (LWP 4592)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 91374

Thread 9 (Thread -1248400480 (LWP 4593))

#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 Snark 2006-12-04 07:44:55 UTC

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused
it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces
for more information on how to do so. Thanks in advance!

Additionnally, explanations in french, german or english have a better chance to make sense to us.

Comment 2 Damien Sandras 2006-12-04 08:56:07 UTC


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