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 702749 - evolution-calendar-factory hangs up on sending meeting notifications to contacts from Google addressbook
evolution-calendar-factory hangs up on sending meeting notifications to conta...
Status: RESOLVED DUPLICATE of bug 704220
Product: evolution-data-server
Classification: Platform
Component: Calendar
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-06-20 13:41 UTC by Vadim Rutkovsky
Modified: 2013-09-21 13:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vadim Rutkovsky 2013-06-20 13:41:14 UTC 
Scenario:
 * Setup Google account
 * Create a contact email
 * Create a new meeting
 * Add created contact with email to attendees list
 * Save meeting and send notifications

Result: evo hangs up, 'timeout is reached' error appears

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

Evo warning:
(evolution:19492): calendar-gui-CRITICAL **: combo_box_changed_cb: assertion 'source != NULL' failed

GDB output:

+ Trace 232119

Thread 1 (Thread 0x7ffff7fa2a40 (LWP 19925))

  • #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 g_dbus_connection_send_message_with_reply_sync
    from /lib64/libgio-2.0.so.0
  • #4 g_dbus_connection_call_sync_internal
    from /lib64/libgio-2.0.so.0
  • #5 g_dbus_proxy_call_sync_internal
    from /lib64/libgio-2.0.so.0
  • #6 g_dbus_proxy_call_sync
    from /lib64/libgio-2.0.so.0
  • #7 e_dbus_calendar_call_send_objects_sync
    from /lib64/libebackend-1.2.so.6
  • #8 e_cal_client_send_objects_sync
    from /lib64/libecal-1.2.so.15
  • #9 itip_send_comp
    from /usr/lib64/evolution/3.10/libevolution-calendar.so
  • #10 real_send_comp
    from /usr/lib64/evolution/3.10/libevolution-calendar.so
  • #11 save_comp_with_send
    from /usr/lib64/evolution/3.10/libevolution-calendar.so
  • #12 save_and_close_editor
    from /usr/lib64/evolution/3.10/libevolution-calendar.so
  • #13 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #14 signal_emit_unlocked_R
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #17 _gtk_action_emit_activate
    from /lib64/libgtk-3.so.0
  • #18 button_clicked
    from /lib64/libgtk-3.so.0
  • #19 _g_closure_invoke_va
    from /lib64/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #22 gtk_real_button_released
    from /lib64/libgtk-3.so.0
  • #23 _g_closure_invoke_va
    from /lib64/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #26 gtk_button_button_release
    from /lib64/libgtk-3.so.0
  • #27 _gtk_marshal_BOOLEAN__BOXEDv
    from /lib64/libgtk-3.so.0
  • #28 _g_closure_invoke_va
    from /lib64/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #31 gtk_widget_event_internal
    from /lib64/libgtk-3.so.0
  • #32 propagate_event
    from /lib64/libgtk-3.so.0
  • #33 gtk_main_do_event
    from /lib64/libgtk-3.so.0
  • #34 gdk_event_source_dispatch
    from /lib64/libgdk-3.so.0
  • #35 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #36 g_main_context_iterate.isra.22
    from /lib64/libglib-2.0.so.0
  • #37 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #38 gtk_main
    from /lib64/libgtk-3.so.0
  • #39 main 






Comment 1


Matthew Barnes





          2013-06-20 13:59:42 UTC
        



This looks like an Evolution backtrace.  Can you post a backtrace for evolution-calendar-factory while hung?






Comment 2


Vadim Rutkovsky





          2013-06-20 14:48:04 UTC
        



The trace from evolution-calendar-factory (though not sure if it helps):





+
Trace
    232120






Thread 1
          (Thread 0x7fda34369840 (LWP 32155))


    

  • 
#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 3


Milan Crha





          2013-08-09 12:06:07 UTC
        




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