dx-packages team mailing list archive

[Renato Araujo Oliveira Filho <renato.filho@xxxxxxxxxxxxx>]

@Charles, I am saving the event time in UTC formart using:

        ECalComponentDateTime *dt = g_new0(ECalComponentDateTime, 1);
        dt->value = g_new0(struct icaltimetype, 1);
        *dt->value = icaltime_from_timet(etr.startDateTime().toTime_t(), etr.isAllDay());
        e_cal_component_set_dtstart(comp, dt);
        e_cal_component_free_datetime(dt);

since there is no way to convert the time to localtime at this point,
could you check if you can do that on the indicator.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1283236

Title:
  Alarms are triggered in UTC tz despite saving in local tz

Status in The Date and Time Indicator:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Confirmed
Status in “qtorganizer5-eds” package in Ubuntu:
  Confirmed

Bug description:
  Setting an alarm in the local timezone is not respected by the system
  since the alarms is triggered in the equivalent UTC timezone.

  Mako build 200, 205

  Steps to reproduce: 
  1. Ensure that phone timezone is something other than UTC. For instance eastern tz (UTC-5)
  2. Set an alarm for 3:00 PM in the ubuntu clock app.
  3. Indicator shows a pending alarm for 3:00 PM
  4. Check a minute or so later, indicator shows an alarm pending for 8:00 PM

  What happens:
  The alarm does not go off at 3:00 PM. Instead it triggers at 8:00 PM

  What should happen:
  The alarm is triggered at 3:00 PM

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1283236/+subscriptions