qtorganizer5-eds

New alarm at 7:28 AM in 33326 days

Bug #1390992 reported by benji
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
qtorganizer5-eds
Confirmed
Critical
Renato Araujo Oliveira Filho

Bug Description

I'm on channel=devel-proposed.

Since 15.04 (r11) the clock apps alarm function seems broken.

No matter what I do, a new alarm I enter is set to 7:28 AM and will be triggered in 33326 days, and a few hours/minutes.

Now still the same on (r14).

Revision history for this message
Dave Morley (davmor2) wrote :

Seems the the new eds might be set to the 1970 date again like it was in utopic.

Revision history for this message
Dave Morley (davmor2) wrote :

This makes sanity tests fail for vivid so should be fixed asap please.

Changed in ubuntu-clock-app:
importance: Undecided → Critical
status: New → Confirmed
tags: added: sanity
tags: added: lt-blocker lt-category-visible lt-prio-high
Nekhelesh Ramananthan (nik90)
affects: ubuntu-clock-app → qtorganizer5-eds
Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

Can we insure a regression test is added to check this in the future?

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

I'm seeing similar results.

Using a Nexus 4 running devel-proposed r28, I created a daily alarm to kick at 7:30 AM. (I'm in -6)

After I hit "save", the alarm showed up in clock-app for 12:28 AM and in indicator-datetime as 11:59 PM.

The tasks.ics created by this reads:

> BEGIN:VCALENDAR
> CALSCALE:GREGORIAN
> PRODID:-//Ximian//NONSGML Evolution Calendar//EN
> VERSION:2.0
> X-EVOLUTION-DATA-REVISION:2014-11-20T19:21:55.008187Z(6)
> BEGIN:VTODO
> UID:20141120T192155Z-3487-32011-1530-9@ubuntu-phablet
> DTSTAMP:20141120T192155Z
> DTSTART:19691231T235959
> DUE:19691231T235959
> RRULE:FREQ=DAILY
> SUMMARY:Alarm
> CATEGORIES:8��^A
> CREATED:20141120T192155Z
> LAST-MODIFIED:20141120T192155Z
> BEGIN:VALARM
> X-EVOLUTION-ALARM-UID:20141120T192155Z-3487-32011-1530-10@ubuntu-phablet
> ACTION:AUDIO
> ATTACH:file:///usr/share/sounds/ubuntu/ringtones/Suru arpeggio.ogg
> END:VALARM
> BEGIN:VALARM
> X-EVOLUTION-ALARM-UID:20141120T192155Z-3487-32011-1530-11@ubuntu-phablet
> ACTION:DISPLAY
> DESCRIPTION:Alarm
> END:VALARM
> END:VTODO
> END:VCALENDAR

* The CREATED and LAST-MODIFIED fields are correct in GMT

* The CATEGORIES field appears to be corrupt. Thinking out loud, maybe this is why i-datetime and clock-app give such different results?

* DTSTART and DUE of 19691231T235959: looks like a -1 status value is being used as a valid time_t somewhere.

* DTSTART and DUE are not needed for repeating VTODO items, although that's probably a topic for a separate ticket. (http://www.kanzaki.com/docs/ical/vtodo.html#descr)

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

FWIW, things are working fine on krilling + rtm r166.

In IRC renato said this may just be that Vivid didn't get updated to the new qtorganizer, and this will get merged soon.

Assigning to Renato just for tracking, but it sounds like this is just a packaging issue.

Changed in qtorganizer5-eds:
assignee: nobody → Renato Araujo Oliveira Filho (renatofilho)
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Is this still an issue?

Revision history for this message
Dave Morley (davmor2) wrote :

No

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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