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 702747 - evolution-addressbook-factory hangs up on modifying Google contact photo
evolution-addressbook-factory hangs up on modifying Google contact photo
Status: RESOLVED DUPLICATE of bug 703463
Product: evolution-data-server
Classification: Platform
Component: Contacts
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-06-20 13:14 UTC by Vadim Rutkovsky
Modified: 2013-09-21 13:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vadim Rutkovsky 2013-06-20 13:14:31 UTC
Scenario:
 * Setup Google addressbook
 * Create any contact
 * Set a new contact photo for contact
 * Click Save

Result: evolution hangs up, 'Error modifying contact - timeout was reached' error appear after ~1 minute

Versions:
evolution-data-server-3.9.3-1.fc20.x86_64
evolution-3.9.3-1.fc20.x86_64
libsoup-2.43.2-1.fc20.x86_6

GDB output:

Thread 1 (Thread 0x7f2acd85c840 (LWP 19332))

  • #0 poll
    from /lib64/libc.so.6
  • #1 g_main_context_iterate.isra.22
    from /lib64/libglib-2.0.so.0
  • #2 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #3 dbus_server_run_server
    from /lib64/libebackend-1.2.so.6
  • #4 ffi_call_unix64
    from /lib64/libffi.so.6
  • #5 ffi_call
    from /lib64/libffi.so.6
  • #6 g_cclosure_marshal_generic_va
    from /lib64/libgobject-2.0.so.0
  • #7 _g_closure_invoke_va
    from /lib64/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #10 e_dbus_server_run
    from /lib64/libebackend-1.2.so.6
  • #11 main

Comment 1 Matthew Barnes 2013-06-20 14:01:22 UTC
Looks similar to bug 698912.
Comment 2 Matthew Barnes 2013-06-20 14:04:14 UTC
You might try downgrading libsoup to 2.40 if you can, to help pin this down.
Comment 3 Vadim Rutkovsky 2013-06-20 15:12:06 UTC
With libsoup-2.40.3-1.fc18.x86_64 evolution-addressbook-factory crashes:

Thread 1 (Thread 0x7f025b850840 (LWP 2122))

  • #0 malloc_consolidate
    from /lib64/libc.so.6
  • #1 _int_free
    from /lib64/libc.so.6
  • #2 g_free
    from /lib64/libglib-2.0.so.0
  • #3 g_string_free
    from /lib64/libglib-2.0.so.0
  • #4 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #5 e_vcard_attribute_remove_values
    from /lib64/libebook-contacts-1.2.so.0
  • #6 e_vcard_attribute_free
    from /lib64/libebook-contacts-1.2.so.0
  • #7 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #8 g_list_free_full
    from /lib64/libglib-2.0.so.0
  • #9 vcard_finalize
    from /lib64/libebook-contacts-1.2.so.0
  • #10 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #11 e_book_backend_modify_contacts_finish
    from /lib64/libedata-book-1.2.so.19
  • #12 data_book_complete_modify_contacts_cb
    from /lib64/libedata-book-1.2.so.19
  • #13 g_simple_async_result_complete
    from /lib64/libgio-2.0.so.0
  • #14 complete_in_idle_cb
    from /lib64/libgio-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #16 g_main_context_iterate.isra.22
    from /lib64/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #18 dbus_server_run_server
    from /lib64/libebackend-1.2.so.6
  • #19 ffi_call_unix64
    from /lib64/libffi.so.6
  • #20 ffi_call
    from /lib64/libffi.so.6
  • #21 g_cclosure_marshal_generic_va
    from /lib64/libgobject-2.0.so.0
  • #22 _g_closure_invoke_va
    from /lib64/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #25 e_dbus_server_run
    from /lib64/libebackend-1.2.so.6
  • #26 main

Comment 4 Matthew Barnes 2013-07-07 19:31:34 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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