Bug 604930 – crash in ekiga 3.2.6

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 604930 - crash in ekiga 3.2.6


Summary:	crash in ekiga 3.2.6


Status:	RESOLVED DUPLICATE of bug 597637

Product:	ekiga
Classification:	Applications
Component:	general
Version:	3.2.x
Hardware:	Other Linux

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

URL:
Whiteboard:

Duplicates:	606094 (view as bug list)
Depends on:
Blocks:

Reported:	2009-12-18 16:38 UTC by Peter Robinson
Modified:	2010-02-20 21:55 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Peter Robinson 2009-12-18 16:38:04 UTC

Crash in ekiga 3.2.6 in Fedora 12 x64

ekiga-3.2.6-1.fc12.x86_64
opal-3.6.6-1.fc12.x86_64
ptlib-2.6.5-1.fc12.x86_64

[New Thread 4553]
[New Thread 4554]
[New Thread 4566]
[New Thread 4565]
[New Thread 4562]
[New Thread 4551]
[New Thread 4560]
[New Thread 4552]
[New Thread 4555]
[New Thread 4561]
[New Thread 4556]
Core was generated by `ekiga'.
Program terminated with signal 11, Segmentation fault.

+ Trace 219670

Thread 11 (Thread 4561)

#0 select
at ../sysdeps/unix/syscall-template.S line 82
#1 PSocket::Select
at ptlib/unix/socket.cxx line 332
#2 PSocket::Select
at ptlib/common/sockets.cxx line 1048
#3 PMonitoredSockets::ReadFromSocket
at ptclib/psockbun.cxx line 588
#4 PMonitoredSocketBundle::ReadFromBundle
at ptclib/psockbun.cxx line 992
#5 OpalListenerUDP::Accept
at /usr/src/debug/opal-3.6.6/src/opal/transports.cxx line 734
#6 OpalListener::ListenForConnections
at /usr/src/debug/opal-3.6.6/src/opal/transports.cxx line 472
#7 PThread::PX_ThreadStart
at ptlib/unix/tlibthrd.cxx line 437
#8 start_thread
at pthread_create.c line 297
#9 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
#10 ??

Thread 6 (Thread 4562)

#0 select
at ../sysdeps/unix/syscall-template.S line 82
#1 PThread::PXBlockOnIO
at ptlib/unix/tlibthrd.cxx line 983
#2 PChannel::PXSetIOBlock
at ptlib/unix/channel.cxx line 120
#3 PSocket::os_accept
at ptlib/unix/socket.cxx line 210
#4 PTCPSocket::Accept
at ptlib/common/sockets.cxx line 2363
#5 OpalListenerTCP::Accept
at /usr/src/debug/opal-3.6.6/src/opal/transports.cxx line 625
#6 OpalListener::ListenForConnections
at /usr/src/debug/opal-3.6.6/src/opal/transports.cxx line 472
#7 PThread::PX_ThreadStart
at ptlib/unix/tlibthrd.cxx line 437
#8 start_thread
at pthread_create.c line 297
#9 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
#10 ??

Thread 1 (Thread 4550)

#0 std::_Rb_tree_increment
at ../../../../libstdc++-v3/src/tree.cc line 63
#1 operator++
at /usr/include/c++/4.4.1/bits/stl_tree.h line 184
#2 visit_objects
at ../../../../lib/engine/framework/reflister.h line 108
#3 Ekiga::HeapImpl<Ekiga::URIPresentity>::visit_presentities
at ../../../../lib/engine/presence/heap-impl.h line 126
#4 Avahi::Heap::BrowserCallback
at ../../../../lib/engine/components/avahi/avahi-heap.cpp line 209
#5 avahi_service_browser_event
at browser.c line 777
#6 filter_func
at client.c line 247
#7 dbus_connection_dispatch
at dbus-connection.c line 4444
#8 dispatch_timeout_callback
at ../avahi-common/dbus-watch-glue.c line 107
#9 start_timeout_callback
at glib-watch.c line 254
#10 dispatch_func
at glib-watch.c line 333
#11 g_main_dispatch
at gmain.c line 1960
#12 IA__g_main_context_dispatch
at gmain.c line 2513
#13 g_main_context_iterate
at gmain.c line 2591
#14 IA__g_main_loop_run
at gmain.c line 2799
#15 IA__gtk_main
at gtkmain.c line 1218
#16 main
at gui/main.cpp line 4592

Comment 1 Snark 2009-12-19 07:00:09 UTC

What where you doing when it crashed?

Comment 2 Peter Robinson 2009-12-26 23:49:48 UTC

Apparently hanging up a call using the red hang up button. We've had 3 dupes of this to date:

https://bugzilla.redhat.com/show_bug.cgi?id=539541
https://bugzilla.redhat.com/show_bug.cgi?id=539633
https://bugzilla.redhat.com/show_bug.cgi?id=546715

1.accept incoming call from asterisk pbx
2.Complete call and click on red phone to hang up

Comment 3 Eugen Dedu 2010-01-11 22:04:47 UTC

From bug #606094, a duplicate:

"In Fedora 12 I've seen a couple of occurrences of the following crash in the
avahi link-local

ekiga-3.2.6-1.fc12
ptlib-2.6.5-1.fc12
opal-3.6.6-1.fc12

The user can reliably crash ekiga with the following steps:

1. connect two Ekiga instances (A and B), running on 2 different F12
installations, to the same Asterisk server;
2. wait for B and A to show up in the respective neighbour lists;
3. call B from A by double clicking the B entry in the neighbour list;
4. B answers the call;
5. 5s or so later A closes the call;
6. just a few seconds later Ekiga instance B exits with Ctrl-Q;
7. right after the A Ekiga instance crashes."

Comment 4 Eugen Dedu 2010-01-11 22:05:11 UTC

*** Bug 606094 has been marked as a duplicate of this bug. ***

Comment 5 Eugen Dedu 2010-02-20 21:55:25 UTC

It's pretty sure this is bug 597637.

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