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 646709 - Evolution crashes when replying to calendar invitation
Evolution crashes when replying to calendar invitation
Status: RESOLVED DUPLICATE of bug 597567
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-04-04 12:56 UTC by ville.ranki
Modified: 2011-04-04 14:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ville.ranki 2011-04-04 12:56:43 UTC 
I have received an calendar invitation by mail (probably sent via outlook). 

Clicking on 'accept' causes evolution to crash.

Running evolution 2.30.3 on Ubuntu Maverick x86_32.


Backtrace:

(gdb) bt full

+ Trace 226578

  • #0 comp_subject
    at itip-utils.c line 673
  • #1 itip_send_comp
    at itip-utils.c line 1323
  • #2 view_response_cb
    at itip-formatter.c line 2092
  • #3 g_cclosure_marshal_VOID(int0_t)
    from /usr/lib/libgobject-2.0.so.0
  • #4 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #5 ??
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #8 button_clicked_cb
    at itip-view.c line 786
  • #9 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0 






Comment 1


Fabio Durán Verdugo





          2011-04-04 14:21:04 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 597567 ***