Bug 468103
| Summary: | Evolution & google calendar username empty | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christoph Höger <choeger> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 9 | CC: | mbarnes, mcrha |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-11-03 10:04:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Christoph Höger
2008-10-22 20:13:50 UTC
The patch from the mentioned bug has no effect on the underlying data, it just doesn't show them properly, even the value is there. I guess, it's the other issue you are facing. Could you look into gconf key /apps/evolution/calendar/sources to the key where the google setup is stored (its group name is "Google") and check whether the right values are there? I recall some issue with stored username, but when wrote with an '@' in it, Evolution was able to break the URL quite well. It has been fixed too, but in F10/rawhide only. It can be also other issue, though. Can you run evolution on console and see whether it prints some error information there when trying to refresh the google calendar, please? Or does it give any error in the UI at all? Currently I get the following error output: (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed (evolution:4774): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART. Skipping... libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART. Skipping... libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART. Skipping... libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART. Skipping... libecal-Message: e_cal_recur_generate_instances_of_rule(): bogus component, does not have DTSTART. Skipping... I had a look at the evolution source and found out, that there is currently _no_ code for recurring events. That explains quite good, why I cannot see any events, as all my tasks are recurring so far. I'll see if I can write a patch to fix that (code seems pretty simple right now), but as gnome is stable right now, it will probably rejected upstream for the current stable release. Would you be willing to backport it at least for fedora 10 (if it really works)? Thanks for your info. Some basic recurrence support has been done already, even still waiting for the review at http://bugzilla.gnome.org/show_bug.cgi?id=508496 I'm closing this in favor of the upstream bug. |