! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
VALARM not correctly interpreted?
Status:
CLOSED: FIXED

Comments

Description lars.taeuber 2011-03-21 09:49:20 CET
Hi,

maybe this bug is still present in newer version. But i only use the standard ubuntu version 4.6.1.

This is my *.ics entry:

BEGIN:VEVENT
UID:Orage-20090915Txxxxxxxx-xxxx@xxxxxx
CLASS:PUBLIC
DTSTAMP:20110321T082815Z
CREATED:20090915T071543Z
LAST-MODIFIED:20110321T082815Z
SUMMARY:radiotatort
DESCRIPTION:radiotatort
DTSTART;VALUE=DATE:20090921
DURATION:PT0S
TRANSP:OPAQUE
RRULE:FREQ=MONTHLY;BYDAY=-2MO

BEGIN:VALARM
TRIGGER;VALUE=DURATION:P1D
X-ORAGE-PERSISTENT-ALARM:YES
ACTION:DISPLAY
DESCRIPTION:radiotatort
X-ORAGE-DISPLAY-ALARM:ORAGE
END:VALARM

BEGIN:VALARM
TRIGGER;VALUE=DURATION:P1D
X-ORAGE-PERSISTENT-ALARM:YES
ACTION:AUDIO
ATTACH:/usr/share/orage/sounds/Spo.wav
REPEAT:7
DURATION:PT4M10S
END:VALARM

END:VEVEN

But the Alarm start on the same day as it is filed for.

This is a bit special:
The event is on the pre last monday of every month. One day after this monday I can download something from the internet. That's why i wanted the alarm start on the tuesday of the pre last monday of every month.

But the alarm starts on the monday.
I think this is a bug or did I something wrong?

Thanks
Lars
Comment 1 juha editbugs 2011-03-22 08:58:00 CET
Yes, there is something wrong. I can reproduce this with the latest version also.
Comment 2 juha editbugs 2011-07-07 08:20:10 CEST
Fixed in 4.8.1.3 available in git now.
Comment 3 juha editbugs 2011-09-20 21:53:54 CEST
Fix in 4.8.2

Bug #7427

Reported by:
lars.taeuber
Reported on: 2011-03-21
Last modified on: 2011-09-20

People

CC List:
0 users

Version

Attachments

Additional information