Bug 408846 – crash in Ekiga Softphone: initialising gnome - but...

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 408846 - crash in Ekiga Softphone: initialising gnome - but...


Summary:	crash in Ekiga Softphone: initialising gnome - but...


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-17 08:30 UTC by cblanquer
Modified:	2007-02-17 13:38 UTC

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

Description cblanquer 2007-02-17 08:30:36 UTC

Version: 2.0.3

What were you doing when the application crashed?
initialising gnome - but I have a bug in this session due to Compiz. It is uninstalled now but the windows are wrong.


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

Memory status: size: 107102208 vsize: 0 resident: 107102208 share: 0 rss: 27406336 rss_rlim: 0
CPU usage: start_time: 1171700880 rtime: 0 utime: 138 stime: 0 cutime:122 cstime: 0 timeout: 16 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 -1246824784 (LWP 5124)]
[New Thread -1290970208 (LWP 5795)]
[New Thread -1290703968 (LWP 5794)]
[New Thread -1290437728 (LWP 5793)]
[New Thread -1290171488 (LWP 5792)]
[New Thread -1288234080 (LWP 5781)]
[New Thread -1287967840 (LWP 5780)]
[New Thread -1285239904 (LWP 5653)]
[New Thread -1310418016 (LWP 5525)]
[New Thread -1311769696 (LWP 5523)]
[New Thread -1248752736 (LWP 5385)]
[New Thread -1248486496 (LWP 5384)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 111442

Thread 11 (Thread -1248752736 (LWP 5385))

#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 Susana 2007-02-17 13:38:25 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

This issue is already fixed. Thanks.

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