! 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 !
Orage keeps notifying every second on "All day events"
Status:
CLOSED: FIXED
Severity:
critical

Comments

Description Jerome 2012-03-03 01:14:55 CET
If I create an "All day event" with an alarm (eg. a birthday), when the alarm time has come, orage keeps notifying every second : the default orage alarm windows accumulate on the screen. If notification is enabled, on screen notifications soon fill the screen.

This happens whether "persistent alarm" is checked or not.

This does not happen if a start time and an end time are provided instead of the "All day event" option being checked.

BEGIN:VEVENT
UID:Orage-20120302T235415Z2-1000@bouzin
CLASS:PUBLIC
DTSTAMP:20120303T001340Z
CREATED:20120302T235415Z
LAST-MODIFIED:20120303T001340Z
SUMMARY:This raises an issue
DTSTART;VALUE=DATE:20120305
DURATION:PT0S
TRANSP:OPAQUE
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-P1DT23H2M
ACTION:DISPLAY
DESCRIPTION:This raises an issue
X-ORAGE-DISPLAY-ALARM:ORAGE
END:VALARM
END:VEVENT

BEGIN:VEVENT
UID:Orage-20120302T235415Z2-1000@bouzin
CLASS:PUBLIC
DTSTAMP:20120303T001413Z
CREATED:20120302T235415Z
LAST-MODIFIED:20120303T001413Z
SUMMARY:This is all right
DTSTART;TZID=Europe/Paris:20120305T000000
DURATION:PT23H59M
TRANSP:OPAQUE
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-P1DT23H2M
ACTION:DISPLAY
DESCRIPTION:This is all right
X-ORAGE-DISPLAY-ALARM:ORAGE
END:VALARM
END:VEVENT

Orage version 4.8.3 (up-to-date debian wheezy).

I set it as critical as the windows that keep appearing almost prevent the user from doing anything to stop orage from sending alarms.

Feel free to ask for more tests if needed.
Comment 1 juha editbugs 2012-03-03 10:00:48 CET
Tested and this reproduces on my system also.
Comment 2 juha editbugs 2012-03-03 10:02:31 CET
Note to self: It adds negative offset alarm.
Comment 3 Jerome 2012-03-03 10:53:33 CET
Further investigation :

Bad
DTSTART;VALUE=DATE:20120305
DURATION:PT0S

Good
DTSTART;TZID=Europe/Paris:20120305T000000
DURATION:PT23H59M

Good
DTSTART;TZID=Europe/Paris:20120305T000000
DURATION:PT0S

It seems to be about the DTSTART property. As far as I understand, DTSTART;VALUE=DATE:20120305 is allowed by RFC 5545 : 
http://tools.ietf.org/html/rfc5545#section-3.8.2.4

Am I wrong ? 

Or would the error be in the way orage deals with the yet-correct-as-regard-to-the-RFC "DTSTART;VALUE=DATE:20120305" property ?
Comment 4 juha editbugs 2012-03-04 13:15:05 CET
This is now fixed in 4.8.3.1 available in git.

Yes, there was a bug in handling full day events.
(And yes, full day events are type VALUE=DATE:20120305 as you mentioned andthey
are fully ok.)
Comment 5 Jerome 2012-03-04 13:27:03 CET
Great, thanks.

I was asking about VALUE=DATE:20120305 because I've been working on an .ics export for gbirthday, and along with the RFC, I got inspiration from the .ics generated by orage, and I used the VALUE=DATE:20120305 property.
Comment 6 juha editbugs 2013-02-01 13:33:32 CET
Available in Orage 4.8.4

Bug #8525

Reported by:
Jerome
Reported on: 2012-03-03
Last modified on: 2013-02-01

People

CC List:
0 users

Version

Attachments

Additional information