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 651033 - Evolution crash when accepting new meeting
Evolution crash when accepting new meeting
Status: RESOLVED DUPLICATE of bug 597567
Product: evolution
Classification: Applications
Component: Calendar
3.0.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-05-25 07:39 UTC by Lionel Landwerlin
Modified: 2011-06-21 11:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Lionel Landwerlin 2011-05-25 07:39:15 UTC 
With evolution 3.0.0 : 

(evolution:31907): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed
[Thread 0x7fffd4cdf700 (LWP 31926) exited]
[Thread 0x7fffcf7fe700 (LWP 31920) exited]
[Thread 0x7fffd6756700 (LWP 31917) exited]
[Thread 0x7fffd7986700 (LWP 31916) exited]

(evolution:31907): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed

Program received signal SIGSEGV, Segmentation fault.
comp_subject (method=<value optimized out>, comp=<value optimized out>)
    at itip-utils.c:700
700	itip-utils.c: No such file or directory.
	in itip-utils.c
(gdb) bt
(gdb) bt

+ Trace 227241

  • #0 comp_subject
    at itip-utils.c line 700
  • #1 itip_send_comp
    at itip-utils.c line 1433
  • #2 view_response_cb
    at itip-formatter.c line 2223
  • #3 g_closure_invoke
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gclosure.c line 767
  • #4 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 3252
  • #5 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 2983
  • #6 g_signal_emit
  • #7 g_closure_invoke
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gclosure.c line 767
  • #8 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 3252
  • #9 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 2983
  • #10 g_signal_emit
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 3040
  • #11 ??
    from /usr/lib/libgtk-3.so.0
  • #12 g_closure_invoke
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gclosure.c line 767
  • #13 signal_emit_unlocked_R
  • #14 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 2983
  • #15 g_signal_emit
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 3040
  • #16 ??
    from /usr/lib/libgtk-3.so.0
  • #17 ??
    from /usr/lib/libgtk-3.so.0
  • #18 g_closure_invoke
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gclosure.c line 767
  • #19 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 3290
  • #20 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 2993
  • #21 g_signal_emit
    at /tmp/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 3040
  • #22 ??
    from /usr/lib/libgtk-3.so.0
  • #23 gtk_propagate_event
    from /usr/lib/libgtk-3.so.0
  • #24 gtk_main_do_event
    from /usr/lib/libgtk-3.so.0
  • #25 ??
    from /usr/lib/libgdk-3.so.0
  • #26 g_main_dispatch
    at /tmp/buildd/glib2.0-2.28.6/./glib/gmain.c line 2440
  • #27 g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.28.6/./glib/gmain.c line 3013
  • #28 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.28.6/./glib/gmain.c line 3091
  • #29 g_main_loop_run
    at /tmp/buildd/glib2.0-2.28.6/./glib/gmain.c line 3299
  • #30 gtk_main
    from /usr/lib/libgtk-3.so.0
  • #31 main
    at main.c line 734 






Comment 1


Milan Crha





          2011-06-21 04:20:07 UTC
        



Thanks for a bug report. This is exactly the same issue like with bug #597567, it seems to me. As mentioned in bug #597567 comment #14, what is the libical version you've the evolution-data-server and evolution compiled against? The comment says the libical 0.46 or higher is required to have this fixed.






Comment 2


Lionel Landwerlin





          2011-06-21 07:31:49 UTC
        



I'm using libical 0.44.






Comment 3


Milan Crha





          2011-06-21 11:41:37 UTC
        



Thanks for the update. Then it explains it, update libical to 0.46, then build evolution related products against it, and the bug will be fixed. I'm marking this as a duplicate of the other bug.

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