Bug: Google calendar not showing all events [not relevant]

asked 2014-03-18 11:35:47 +0200

pekkap
1131 ●7 ●11 ●15

http://www.ee.oulu.fi/~pp...

updated 2014-07-12 19:03:47 +0200

I noticed that in 1.0.4.20 only some google calendar events were showing up. Account wasn't enabled, did that, still no go. Twiddling around the database files I could find the missing events:

echo "SELECT * FROM Components;"|sqlite3 /home/nemo/.local/share/system/privileged/Calendar/mkcal/db | grep

(in fact, 38 copies of the event I was looking for), editing an entry on the web made it show up on the phone.

I did find a way to work around this:

• Move/remove calendar files from /home/nemo/.local/share/system/privileged/Calendar & Calendars. Note that this is a risky operation, so don't try if you're not comfortable with the shell!

Close calendar & open terminal in developer mode

devel-su
mkdir /home/nemo/calbak
mv /home/nemo/.local/share/system/privileged/Calendar/mkcal/db* /home/nemo/calbak
mv /home/nemo/.local/share/system/privileged/Calendars/google.db /home/nemo/calbak

• Removed my google account from the phone completely and recreated it

everything is fine and calendar db is no longer bloated:

[root@localhost mkcal]# ls -l db
-rw-r--r-- 1 nemo privileged 195584 Mar 18 11:18 db 
[root@localhost mkcal]# ls -l ~nemo/calbak/db
-rw-r--r-- 1 nemo privileged 6197248 Mar 18 11:00 /home/nemo/calbak/db

Possible workaround editing sqlite database here: https://together.jolla.com/question/38887/bug-calendar-entries-synced-from-google-account-with-multiple-calendars-dont-have-a-calendar-assigned-in-the-mkal-db-and-are-not-shown-in-the-calendar/#post-id-40071

Some relevant tidbits from https://together.jolla.com/question/23754/google-calendar-synchronization/

"You can trigger it with dbus if you're so inclined: dbus-send --session --type=method_call --print-reply --dest=com.meego.msyncd /synchronizer com.meego.msyncd.startSync string:'google.Calendars' "

"It turns out that the sqlite storage backend for mkcal doesn't delete events from the database when they are deleted (as it keeps them so that it can return them when the client requests events that have been deleted since some timestamp). Previously, we were using the google event id as the event id, and this may have caused issues with resyncing previously synced events (as deletion of the old one followed by creation of the new one, may have failed due to id clash). This will be fixed asap! Thanks for your report!"