hangs when notifying of an incoming connection

[Brian J. Murrell]

Binary package hint: ekiga

$ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
$ apt-cache policy ekiga
ekiga:
  Installed: 2.0.12-0ubuntu2
  Candidate: 2.0.12-0ubuntu2
  Version table:
 *** 2.0.12-0ubuntu2 0
        500 http://apt.interlinx.bc.ca hardy/main Packages
        100 /var/lib/dpkg/status

Occasionally when ekiga displays it's "incoming call" popup the application will hang altogether with the following stack trace:

#0 0xb7f2f410 in __kernel_vsyscall ()
#1 0xb6806aa5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb75f7384 in giop_recv_buffer_get (ent=0xbfa7bdac, timeout=0xbfa7bdc4) at giop-recv-buffer.c:716
#3 0xb75fbe88 in ORBit_small_invoke_stub (obj=0x8894a48, m_data=0xb7861180, ret=0xbfa7be90, args=0xbfa7be88, ctx=0x0,
    ev=0xbfa7bef8) at orbit-small.c:658
#4 0xb75fc095 in ORBit_small_invoke_stub_n (object=0x8894a48, methods=0x31b, index=<value optimized out>, ret=0xbfa7be90,
    args=0xbfa7be88, ctx=0x0, ev=0xbfa7bef8) at orbit-small.c:575
#5 0xb7608812 in ORBit_c_stub_invoke (obj=0x8894a48, methods=0xb78611c4, method_index=0, ret=0xbfa7be90, args=0xbfa7be88,
    ctx=0x0, ev=0xbfa7bef8, class_id=0, method_offset=4,
    skel_impl=0xb783cb90 <_ORBIT_skel_small_GNOME_Evolution_Addressbook_BookFactory_getBook>) at poa.c:2643
#6 0xb783e749 in GNOME_Evolution_Addressbook_BookFactory_getBook (_obj=0x8894a48,
    source=0x8a68370 "<?xml version=\"1.0\"?>\n<source uid=\"1218568818.21532.1273@pc\" name=\"\" uri=\"file:///home/brian/.evolution/addressbook/local/system\"/>\n", listener=0x8c7ece8, ev=0xbfa7bef8) at Evolution-DataServer-Addressbook-stubs.c:330
#7 0xb78461b9 in e_book_new (source=0xb1368250, error=0x0) at e-book.c:3340
#8 0xb78466ee in e_book_new_from_uri (uri=0x8afc580 "file:///home/brian/.evolution/addressbook/local/system", error=0x0)
    at e-book.c:3852
#9 0x080c4486 in ?? ()
#10 0x080bbf96 in ?? ()
#11 0x0808ae64 in ?? ()
#12 0xb74a5081 in IA__g_list_remove_link (list=0xb11db1c0, llink=0x80) at /build/buildd/glib2.0-2.16.4/glib/glist.c:410
#13 0xb74a6bf8 in g_source_destroy_internal (source=0x0, context=0xb11db1c0, have_lock=-1299515048)
    at /build/buildd/glib2.0-2.16.4/glib/gmain.c:893
#14 0xb74a9e5e in g_main_context_iterate (context=0x81454f8, block=1, dispatch=1, self=0x8118530)
    at /build/buildd/glib2.0-2.16.4/glib/gmain.c:2634
#15 0xb74aa1e7 in g_main_context_iterate (context=0xbfa7c1a8, block=139782704, dispatch=-1233107680, self=0x854ea30)
    at /build/buildd/glib2.0-2.16.4/glib/gmain.c:2957
#16 0xb7b08264 in IA__gtk_main () at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c:1163
#17 0x0808e971 in ?? ()
#18 0xb65a0450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#19 0x08069041 in ?? ()

This looks a lot like 257166 which I filed yesterday. I would have just added the above trace to that bug but I have been chastised about putting more than one stack trace in a bug, so here's a new one for this stack trace.

[Brian J. Murrell (brian-interlinx)]

I should add that "evolution --force-shutdown" causes ekiga to resume it's operations and continue working.

[Pedro Villavicencio (pedro)]

is this still an issue with intrepid?

[Brian J. Murrell (brian-interlinx)]

I'm using the ekiga 3.0.0 snapshots currently (i.e. not the ekiga from ubuntu) but given the number of evo address book hangs in other various applications, I would tend to day that yes, this is probably still an issue.

[Andreas Moog (ampelbein)]

Seems like a bug in evolution-data-server to me, considering ekiga is not the only application hanging.

[Pedro Villavicencio (pedro)]

could you get another backtrace if this is still an issue with karmic? thanks.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.