evolution-ews spams dbus.log

[John Kennedy]

on closing evolution today evolution-ews began spamming the dbus.log found in ~/.cache/upstart/dbus.log

this log grew to 66GB in size and only stopped when the disk partition was full thus making the system unusable. Solution was to delete dbus.log from the CLI.

output of ls -l dbus.log spaced 8 minutes apart

USER@???-Thinkpad-X1Carbon:~/.cache/upstart$ ls -l dbus.log
-rw-r----- 1 USER USER 5490535542 Jan 11 22:55 dbus.log
USER@???-Thinkpad-X1Carbon:~/.cache/upstart$ ls -l dbus.log
-rw-r----- 1 USER USER 13996434976 Jan 11 23:03 dbus.log

output of tail dbus.log

USER@???-Thinkpad-X1Carbon:~/.cache/upstart$ tail dbus.log

(evolution-calendar-factory:2591): libeews-CRITICAL **: e_ews_notification_get_events_sync: assertion 'notification->priv->connection != NULL' failed

(evolution-calendar-factory:2591): libeews-CRITICAL **: e_ews_notification_get_events_sync: assertion 'notification->priv->connection != NULL' failed

(evolution-calendar-factory:2591): libeews-CRITICAL **: e_ews_notification_get_events_sync: assertion 'notification->priv->connection != NULL' failed

(evolution-calendar-factory:2591): libeews-CRITICAL **: e_ews_notification_get_events_sync: assertion 'notification->priv->connection != NULL' failed

(evolution-calendar-factory:2591): libeews-CRITICAL **: e_ews_notification_get_events_sync: assertion 'notification->priv->connection != NULL' failed

it appears to be evolution-ews and evolution-calendar-factory that are struggling to interact.

system details

USER@???-Thinkpad-X1Carbon:~/.cache/upstart$ lsb_release -rd
Description: Ubuntu 14.10
Release: 14.10
USER@???-Thinkpad-X1Carbon:~/.cache/upstart$ apt-cache policy evolution-ews
evolution-ews:
  Installed: 3.12.7-1
  Candidate: 3.12.7-1
  Version table:
 *** 3.12.7-1 0
        500 http://au.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
        100 /var/lib/dpkg/status

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jason Yang (populus117)]

Can also stop the log file from growing by killing evolution-calendar-factory

[Kervin Pierre (kervin-x)]

This bug happens after you kill 'evolution' process. You also have to kill evolution-calendar-factory otherwise it generates about a gig of logs per minute.