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 648369 - Linking Google calendar to Evolution caused crash
Linking Google calendar to Evolution caused crash
Status: RESOLVED INCOMPLETE
Product: evolution-data-server
Classification: Platform
Component: general
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[google]
Depends on:
Blocks:
 
 
Reported: 2011-04-21 12:50 UTC by Pedro Villavicencio
Modified: 2011-08-11 05:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Description Pedro Villavicencio 2011-04-21 12:50:44 UTC 
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/762993

"I was just finishing the process of linking my Google calendar with Evolution. I had already retrieved my list of calendars, selected the one I wanted, and put in my password for the second time. Evolution simply closed."

".

+ Trace 226820

Thread 1 (Thread 2586)

  • #0 rebuild_model
    at e-source-selector.c line 365
  • #1 on_idle_rebuild_model_callback
    at e-source-selector.c line 479
  • #2 g_idle_dispatch
    at /build/buildd/glib2.0-2.28.5/./glib/gmain.c line 4545
  • #3 g_main_dispatch
    at /build/buildd/glib2.0-2.28.5/./glib/gmain.c line 2440
  • #4 g_main_context_dispatch
    at /build/buildd/glib2.0-2.28.5/./glib/gmain.c line 3013
  • #5 g_main_context_iterate
    at /build/buildd/glib2.0-2.28.5/./glib/gmain.c line 3091
  • #6 g_main_loop_run
    at /build/buildd/glib2.0-2.28.5/./glib/gmain.c line 3299
  • #7 IA__gtk_main
    at /build/buildd/gtk+2.0-2.24.4/gtk/gtkmain.c line 1257
  • #8 main
    at main.c line 715 






Comment 1


Milan Crha





          2011-06-29 11:54:10 UTC
        



Thanks for a bug report. This can be related to bug #633780, as the patch from there touches approximately the same line numbers. If it's reproducible at your user, could you test that patch there, please?






Comment 2


Akhil Laddha





          2011-08-11 05:53:48 UTC
        



Please feel free to reopen the bug if the problem still occurs with a newer
version of Evolution 3.0.2 or later, thanks.