Google calendar does not display events prior to installation

Bug #1563570 reported by Thomas Meyssonnier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Calendar App
Triaged
High
Renato Araujo Oliveira Filho

Bug Description

When I first started Calendar, the events recorded in my Google calendar showed up.
At some point they disappeared, though those created through Calendar were still visible.
I know they must be somewhere because some recurring events still show up on my Pebble smartwatch, which (if I'm not mistaken) takes its data from the phone and not directly from Google.

Thanks,
TM

Revision history for this message
Thomas Meyssonnier (thomas-meyssonnier) wrote :

Update:
It seems something has deleted all my preceding calendar events, according to Google Calendar website.
I don't really mind, but this is a heavy malfunction and some people might find it disastrous.
Plus, as I said, the deleted information still shows up elsewhere and I have no means to access it, so for instance I have duplicate recurrent events (I re-created a missing event), which seem to be confused (modifying the one I can see also alters the other). I have no idea how to get rid of the duplicate event, seeing as I can't reach it, either in Calendar or through Google.

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

hmn, this sounds quite bad.
@renato please work with Thomas to request needed information to help debug this.
@thomas, please attach all of your logs from ~/.cache/upstart/sync-monitor.log

Changed in ubuntu-calendar-app:
assignee: nobody → Renato Araujo Oliveira Filho (renatofilho)
importance: Undecided → High
milestone: none → 0.6
status: New → Triaged
Revision history for this message
Thomas Meyssonnier (thomas-meyssonnier) wrote : Re: [Bug 1563570] Google calendar does not display events prior toinstallation

Here are the logs, but they only go back to 17/04 and it must have happened
around 23/03... Wish I'd known then :(
By the way, synchronization fails regularly a number of times in a row,
especially when switching networks (turning off the Wi-Fi). At least you
should get clues about that.

Le samedi 23 avril 2016 00:57:35 CEST, Bill Filler
<email address hidden> a écrit :
> hmn, this sounds quite bad.
> @renato please work with Thomas to request needed information
> to help debug this.
> @thomas, please attach all of your logs from
> ~/.cache/upstart/sync-monitor.log
>
> ** Changed in: ubuntu-calendar-app
> Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)
>
> ** Changed in: ubuntu-calendar-app
> Importance: Undecided => High
>
> ** Changed in: ubuntu-calendar-app
> Milestone: None => 0.6
>
> ** Changed in: ubuntu-calendar-app
> Status: New => Triaged
>

--
Message envoyé via Dekko depuis mon appareil Ubuntu

Revision history for this message
Renato Araujo Oliveira Filho (renatofilho) wrote :

Ok based on the logs your syncevolution is failing to sync your events due some conflicts with local and remote events. (I never saw this error, I will need to dig on syncevolution to try to solve it, and this can take a while).

As as short term solution you can manually trigger a refresh from server sync (it will remove all local changes, and sync all events from server).

1 - Check your account id (it will list all online accounts and account id, looks for the account that you want to sync):
      account-console list

2 - Do a manual sync (Example: syncevolution --sync refresh-from-remote google-calendar-1)
      syncevolution --sync refresh-from-remote google-calendar-<account-id>

Revision history for this message
Thomas Meyssonnier (thomas-meyssonnier) wrote :

OK, this seems to have worked for the moment, and Calendar seems to sync
again without problems.
I still did have 'revenant' duplicate events, which probably came from
recreating events that disappeared spontaneously at some point. Trying to
remove those revealed there might be a confusion between events with the
same name and time (I tried to delete one that showed up as one-time and it
still asked if it should affect the whole series, which was a property of
the other).
Name and time don't make up a unique key, in terms of database, unless you
expressly forbid to create doubles. I don't think Google does that, so
you'd need to refer to the actual OID (if Google API agrees to reveal it).
Seeing as almost anything could happen behind Calendar's back (for instance
two events switching properties completely), the risk of confusion exists
so long as you don't use the right key... So if Google refuses to cooperate
it's virtually impossible to run a concurrent app.

Sorry for my lengthy explanation, and thanks for the quick and dirty fix,
should work now.

TM

Le lundi 25 avril 2016 15:47:12 CEST, Renato Araujo Oliveira Filho
<email address hidden> a écrit :
> Ok based on the logs your syncevolution is failing to sync your events
> due some conflicts with local and remote events. (I never saw this
> error, I will need to dig on syncevolution to try to solve it, and this
> can take a while).
>
> As as short term solution you can manually trigger a refresh from
> server sync (it will remove all local changes, and sync all events from
> server).
>
> 1 - Check your account id (it will list all online accounts and
> account id, looks for the account that you want to sync):
> account-console list
>
> 2 - Do a manual sync (Example: syncevolution --sync
> refresh-from-remote google-calendar-1)
> syncevolution --sync refresh-from-remote google-calendar-<account-id>
>

--
Message envoyé via Dekko depuis mon appareil Ubuntu

Revision history for this message
Thomas Meyssonnier (thomas-meyssonnier) wrote :

Sorry to interrupt again, but I'm having funny stuff with this revenent
event. For some reason it resists flushing Calendar's memory with Google's.
It persists showing up twice in Calendar, even though it's disappeared from
Google altogether (both instances).
There's a real recurring event, and something that looks like a single
instance of a non-existing recurring event. I wonder where it resides
because it seems a one-way sync from Google doesn't make it disappear.
I do also have a Pebble watch that keeps track of my calendar, with a
separate authorization. So maybe RockWork (Ubuntu phone framework for
Pebble) is to blame for that. Shouldn't sync upwards but you never know.
Sometimes I wonder if it's not my mind that's failing, more than the
computer :p. I'm pretty good at creating confusing situations
unintentionally.

Le lundi 25 avril 2016 15:47:12 CEST, Renato Araujo Oliveira Filho
<email address hidden> a écrit :
> Ok based on the logs your syncevolution is failing to sync your events
> due some conflicts with local and remote events. (I never saw this
> error, I will need to dig on syncevolution to try to solve it, and this
> can take a while).
>
> As as short term solution you can manually trigger a refresh from
> server sync (it will remove all local changes, and sync all events from
> server).
>
> 1 - Check your account id (it will list all online accounts and
> account id, looks for the account that you want to sync):
> account-console list
>
> 2 - Do a manual sync (Example: syncevolution --sync
> refresh-from-remote google-calendar-1)
> syncevolution --sync refresh-from-remote google-calendar-<account-id>
>

--
Message envoyé via Dekko depuis mon appareil Ubuntu

Revision history for this message
Thomas Meyssonnier (thomas-meyssonnier) wrote :

Sorry for thea excessive email, but this is what I came up with to get rid
of inconsistencies:
Remove and create again the Google account.
This does get Calendar to purge its data, which I couldn't get done with
what you suggested (there must be data remaining somewhere if you do that,
another weird bug but maybe nobody else will run into it again...).
I think it could have been done with syncevolution --delete-items, but I
spent hours trying to find the name of the datastore, unsuccessfully. The
documentation isn't really open to beginners, unfortunately.
I guess recovering from mess-ups is the step just after getting things to
work in the first place. I usually don't get that far, since I only work on
experimental stuff. Guess it's quite another business.

Thanks anyway,
Thomas

Le lundi 25 avril 2016 15:47:12 CEST, Renato Araujo Oliveira Filho
<email address hidden> a écrit :
> Ok based on the logs your syncevolution is failing to sync your events
> due some conflicts with local and remote events. (I never saw this
> error, I will need to dig on syncevolution to try to solve it, and this
> can take a while).
>
> As as short term solution you can manually trigger a refresh from
> server sync (it will remove all local changes, and sync all events from
> server).
>
> 1 - Check your account id (it will list all online accounts and
> account id, looks for the account that you want to sync):
> account-console list
>
> 2 - Do a manual sync (Example: syncevolution --sync
> refresh-from-remote google-calendar-1)
> syncevolution --sync refresh-from-remote google-calendar-<account-id>
>

--
Message envoyé via Dekko depuis mon appareil Ubuntu

Bill Filler (bfiller)
Changed in ubuntu-calendar-app:
milestone: 0.6 → backlog
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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