Bug 369748 – crash in Ekiga Softphone: I killed X because it wa...

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 369748 - crash in Ekiga Softphone: I killed X because it wa...


Summary:	crash in Ekiga Softphone: I killed X because it wa...


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-11-03 00:14 UTC by Jukka Hellen
Modified:	2006-11-03 01:06 UTC

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

Description Jukka Hellen 2006-11-03 00:14:36 UTC

Version: 2.0.3

What were you doing when the application crashed?
I killed X because it wasn't responing. Logged in again and Ekiga crashed at login.


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

Memory status: size: 141873152 vsize: 0 resident: 141873152 share: 0 rss: 20135936 rss_rlim: 0
CPU usage: start_time: 1162478371 rtime: 0 utime: 84973 stime: 0 cutime:83811 cstime: 0 timeout: 1162 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 -1247753552 (LWP 5416)]
[New Thread -1297888352 (LWP 22492)]
[New Thread -1298154592 (LWP 6340)]
[New Thread -1297355872 (LWP 6289)]
[New Thread -1297089632 (LWP 6288)]
[New Thread -1295746144 (LWP 6013)]
[New Thread -1295053920 (LWP 6003)]
[New Thread -1370588256 (LWP 6000)]
[New Thread -1249907808 (LWP 5812)]
[New Thread -1249641568 (LWP 5811)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 82135

Thread 9 (Thread -1249907808 (LWP 5812))

#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 André Klapper 2006-11-03 01:06:50 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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