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 609556 - Added iCal Subscription from 30boxes.com events not displayed in evolution
Added iCal Subscription from 30boxes.com events not displayed in evolution
Status: RESOLVED DUPLICATE of bug 429317
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-02-10 17:14 UTC by Steve Bamber
Modified: 2010-02-11 05:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Steve Bamber 2010-02-10 17:14:27 UTC
+++ This bug was initially created as a clone of Bug #429317 +++

Steps to reproduce:
1. create a calendar on 30boxes.com
2. get webcal:// address of calendar from 30boxes settings page
3. add an on the web calendar to evolution using that webcal:// address
4. events are not displayed in evolution

Other information:

Gentoo package versions

gnome-extra/evolution-data-server-2.28.2 
gnome-extra/evolution-webcal-2.28.0 
mail-client/evolution-2.28.2 

Bug 429317 reported a crash in the data-server which was fixed in 2.24 and events would then appear in the calendar without issue.

Upgraded to 2.28 and whilst the data server doesn't crash, no events are displayed in evolution.
Comment 1 Akhil Laddha 2010-02-11 04:26:13 UTC
Patch wasn't committed in 2.25.x on that time period so it shouldn't be there in 2.28.x. I committed in 2.29.x so it will be a part of 2.30.x stable release. 

Anyway i will try to commit to 2.28.x if patch applies without any issue.
Comment 2 Akhil Laddha 2010-02-11 05:22:55 UTC
I have committed patch in stable branch (2.28.x)

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 429317 ***