Ubuntu RTM
indicator-datetime package

Alarms and calendar events disappeared from indicator-datetime

Bug #1415872 reported by Ricardo Salveti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu RTM)
Confirmed
Low
Charles Kerr

Bug Description

current build number: 220
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-01-28 12:00:02
version version: 220
version ubuntu: 20150128
version device: 20150126-cb82dc1
version custom: 20150127-526-24-181

Noticed yesterday that we had a calendar app update, and after doing the updated and requesting a calendar sync, all my alarms and calendar events disappeared from indicator-datetime.

I was also unable to create new alarms (it created fine at the clock-app, but not showing up at indicator-datetime and not ringing at the scheduled time), and it also didn't ring at the scheduled time from my previous alarms (noticed this morning after waking up a bit late because the alarm didn't ring in time :-)

Got one crash for evolution-calendar-factory in /var/crash and the following in the indicator-datetime log file:
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

After restarting indicator-datetime, I was able to see my calendar events and alarms just fine (and was able to create new entries as well).

Revision history for this message
Charles Kerr (charlesk) wrote :

Well, it's clear enough what's happening: when evolution-calendar-factory crashes, it takes all the calendars and alarms down with it. Restarting indicator-datetime asks for e-c-f on the bus, so dbus activates a new copy.

I guess we could add a dbus_name_watch() callback in indicator-datetime that restarts the EDS connections when the name disappears, which would trigger the dbus activation.

In practice that would have an annoying side-effect of requiring us to stop indicator-datetime before EDS is killable, but that's more of a testing/developer frustration than an end-user frustration.

Changed in indicator-datetime (Ubuntu RTM):
assignee: nobody → Charles Kerr (charlesk)
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Would rather focus on resolving the crash

Pat McGowan (pat-mcgowan)
Changed in indicator-datetime (Ubuntu RTM):
importance: Undecided → Low
status: New → Confirmed
no longer affects: canonical-devices-system-image
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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