adding new calendar event doesn't sync to google

Bug #1302182 reported by Bill Filler
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Calendar App
Fix Released
High
Kunal Parmar

Bug Description

If I add a new calendar event in the calendar app, it is not getting synced properly to google and never shows up in the google calendar.

The log shows that it's trying to sync but it never appears in google:

static void ViewWatcher::onObjectsAdded(ECalClientView*, GSList*, ViewWatcher*) 0x19dffb8
syn requested for account: "<email address hidden>" "calendar"
Pushed into queue
Sync requested service: "<email address hidden>" "calendar"
Configure account for service: "<email address hidden>" "calendar"
start configure for services ("calendar")
 config session created "google-calendar-3" "idle"
 account config done "<email address hidden>" "calendar"
virtual QList<QtOrganizer::QOrganizerCollection> QOrganizerEDSEngine::collections(QtOrganizer::QOrganizerManager::Error*)
virtual bool QOrganizerEDSEngine::startRequest(QtOrganizer::QOrganizerAbstractRequest*)
virtual bool QOrganizerEDSEngine::waitForRequestFinished(QtOrganizer::QOrganizerAbstractRequest*, int)
last status "200"
sync Mod QMap(("calendar_uoa_3", "two-way"))
Syncronization "Start sync: <email address hidden> (calendar)"
Sync started "<email address hidden>" "calendar"
Progress 0
sync done with "calendar_uoa_3" "idle"
State changed to "running" during 1
Progress 0
sync done with "calendar_uoa_3" "idle"
sync done with "contacts_uoa_3" "idle"
Status changed invalid; "running;waiting"
sync done with "calendar_uoa_3" "idle"
sync done with "contacts_uoa_3" "idle"
State changed to "running" during 1
sync done with "calendar_uoa_3" "running"
sync done with "contacts_uoa_3" "idle"
State changed to "running" during 1
Progress 38
Progress 69
sync done with "calendar_uoa_3" "running"
sync done with "contacts_uoa_3" "idle"
Status changed invalid; "running;waiting"
sync done with "calendar_uoa_3" "running"
sync done with "contacts_uoa_3" "idle"
State changed to "running" during 1
sync done with "calendar_uoa_3" "done"
sync done with "contacts_uoa_3" "idle"
State changed to "running" during 1
sync done with "calendar_uoa_3" "done"
sync done with "contacts_uoa_3" "idle"
Status changed invalid; "running;waiting"
sync done with "calendar_uoa_3" "done"
sync done with "contacts_uoa_3" "idle"
State changed to "running" during 1
Progress 100
sync done with "calendar_uoa_3" "done"
sync done with "contacts_uoa_3" "idle"
Syncronization "Sync done: <email address hidden> (calendar) Status: 200 "
Sync done "<email address hidden>" "calendar"

Related branches

Revision history for this message
Bill Filler (bfiller) wrote :

note, modifications of existing calendar events that came from google in the calendar app correctly sync back to google. Just not new events created in calendar app.

Changed in sync-monitor:
assignee: nobody → Renato Araujo Oliveira Filho (renatofilho)
importance: Undecided → High
Revision history for this message
Renato Araujo Oliveira Filho (renatofilho) wrote :

The calendar app does not have full support for multiple calendars, creating a new event store it on local calendar which is not synced.

affects: sync-monitor → ubuntu-calendar-app
Changed in ubuntu-calendar-app:
assignee: Renato Araujo Oliveira Filho (renatofilho) → nobody
Bill Filler (bfiller)
Changed in ubuntu-calendar-app:
status: New → Confirmed
assignee: nobody → Kunal Parmar (pkunal-parmar)
Revision history for this message
Kunal Parmar (pkunal-parmar) wrote :

I believe this branch will resolve this issue,
As it lets you choose which calendar to add event to, so if you choose google calendar then event should sync back.

lp:~pkunal-parmar/ubuntu-calendar-app/CalManagement

Mihir Soni (mihirsoni)
Changed in ubuntu-calendar-app:
status: Confirmed → In Progress
Changed in ubuntu-calendar-app:
status: In Progress → Fix Committed
Changed in ubuntu-calendar-app:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.