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 669068 - clicking between week / work week / list / day / month views in calendars locks evo up hard
clicking between week / work week / list / day / month views in calendars loc...
Status: RESOLVED DUPLICATE of bug 673197
Product: evolution-data-server
Classification: Platform
Component: general
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-01-30 22:13 UTC by Máirín Duffy
Modified: 2012-04-27 08:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
backtrace from gdb run of e-calendar-factory (16.47 KB, text/plain)
2012-01-30 22:13 UTC, Máirín Duffy 		Details
IRC log with matt barnes about the problems (7.76 KB, text/plain)
2012-01-30 22:14 UTC, Máirín Duffy 		Details

Description Máirín Duffy 2012-01-30 22:13:22 UTC 
Created attachment 206479 [details]
backtrace from gdb run of e-calendar-factory

evolution-data-server-3.2.3-1.fc16.x86_64
libical-0.48-1.fc16.x86_64
evolution-3.2.3-1.fc16.x86_64

to reproduce consistently, open up evo, click between week /work week / list / day / month views. it will eventually lock up and the only way to recover is to do the following:

pkill -9 evolution
kill -9 any e-calendar-factory processes
restart evolution and don't go anywhere near the calendar
or evolution -c mailer

i'm attaching the trace from "gdb --args /usr/libexec/e-calendar-factory -r" when evolution freezes.

i'm also attaching my log with matt for reference.

it seems upstream has not updated libical which is what causes the bug.
Comment 1 Máirín Duffy 2012-01-30 22:14:17 UTC 
Created attachment 206480 [details]
IRC log with matt barnes about the problems
Comment 2 Milan Crha 2012-04-27 08:59:48 UTC 
Bug #673197 has more detailed information about the issue, thus I'm marking this as a duplicate of it, because both depend on libical 0.48. There is even a link to a workaround on libical side, thus feel free to ask fedora libical maintainer to add it to packages.

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