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 528916 - Calendar does not display Google all-day/multi-day/recurring events
Calendar does not display Google all-day/multi-day/recurring events
Status: RESOLVED DUPLICATE of bug 508496
Product: evolution
Classification: Applications
Component: Calendar
2.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 534287 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-19 15:04 UTC by Jose M. daLuz
Modified: 2008-05-24 15:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Jose M. daLuz 2008-04-19 15:04:57 UTC 
When my Evolution calendar syncs with my Google calendar,  I see all events that have times associated with them. However, I do not see events that are all-day or multi-day without specific times in any view except list view. I also do not see recurring appointments anywhere except list view.

I have tried deleting and recreating the link to my Google calendar without changing this behavior. I have also tried extending the "Day Begins" and "Day Ends" to cover every minute of the day without any luck.

Double-clicking on these events in list view, I get a dialog saying "Validation Error: Event with no start date".

Running Evolution 2.21.1/Gnome 2.21.1 on Gentoo 2007.0.
Comment 1 Jose M. daLuz 2008-04-19 16:49:23 UTC 
(In reply to comment #0)
> Running Evolution 2.21.1/Gnome 2.21.1 on Gentoo 2007.0.
> 
Oops -- 2.22.1 in both cases, not 2.21.1.
Comment 2 Akhil Laddha 2008-05-22 09:36:50 UTC 
*** Bug 534287 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2008-05-22 09:42:01 UTC 
for recurrence issue please refer bug 508496
Comment 4 Jose M. daLuz 2008-05-24 15:57:19 UTC 
(In reply to comment #3)
> for recurrence issue please refer bug 508496
> 
In that case, what I thought was a bug is in fact a feature that hasn't yet been implemented. Thanks for clarifying, I'll mark this as a duplicate of bug 508496.

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