Hi folks,
I'm been running davical 1.1.9.3 in a debian/testing virtual machine
for many years, using Mozilla Thunderbird (formerly the Lightning
plugin) as my primary client. A few days ago I had to force shutdown
and reboot the physical machine hosting the virtual machine because it
appeared to be unresponsive, and since then I've been unable to
successfully mark the latest occurrence of several repeating tasks
(TODOs) as completed. When I click Save to update the task, it
disappears from the reminders dialog, but reappears later (I'm guessing
when Thunderbird refreshes the calendar) or when I restart Thunderbird.
I turned on logging in Thunderbird and I see a WARNING saying:
Lightning: Parsing failed for parts of the item (while this is
considered to be a minor issue, we continue processing the item):
and the following error on each of the problematic VTODO items:
X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE
parameter with an illegal type for property: VALUE=DURATION
The lines that appears to be causing the problem are:
TRIGGER;VALUE=DURATION:-P1D
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:-PT30M
TRIGGER;VALUE=DURATION:-P1D
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:-PT10H
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:-PT12H
TRIGGER;VALUE=DURATION:-PT30M
Each of these is inside a VALARM item. For example:
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-P1D
DESCRIPTION:Default Mozilla Description
END:VALARM
I'm not sure if these warnings are new (corresponding to the recent
problem I'm having) or have been occurring without me know about them
(in which case they might be a red herring). I'm not whether I've
corrupted the database or if my problem is caused by a new version of
davical or Thunderbird. Can someone tell me what is wrong with the
DURATION values and suggest how I can fix them? I've been using psql to
look at the database, and am willing to use it to make modifications if
necessary.
thanks,
Peter
I'm been running davical 1.1.9.3 in a debian/testing virtual machine
for many years, using Mozilla Thunderbird (formerly the Lightning
plugin) as my primary client. A few days ago I had to force shutdown
and reboot the physical machine hosting the virtual machine because it
appeared to be unresponsive, and since then I've been unable to
successfully mark the latest occurrence of several repeating tasks
(TODOs) as completed. When I click Save to update the task, it
disappears from the reminders dialog, but reappears later (I'm guessing
when Thunderbird refreshes the calendar) or when I restart Thunderbird.
I turned on logging in Thunderbird and I see a WARNING saying:
Lightning: Parsing failed for parts of the item (while this is
considered to be a minor issue, we continue processing the item):
and the following error on each of the problematic VTODO items:
X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE
parameter with an illegal type for property: VALUE=DURATION
The lines that appears to be causing the problem are:
TRIGGER;VALUE=DURATION:-P1D
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:-PT30M
TRIGGER;VALUE=DURATION:-P1D
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:-PT10H
TRIGGER;VALUE=DURATION:PT0S
TRIGGER;VALUE=DURATION:-PT12H
TRIGGER;VALUE=DURATION:-PT30M
Each of these is inside a VALARM item. For example:
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-P1D
DESCRIPTION:Default Mozilla Description
END:VALARM
I'm not sure if these warnings are new (corresponding to the recent
problem I'm having) or have been occurring without me know about them
(in which case they might be a red herring). I'm not whether I've
corrupted the database or if my problem is caused by a new version of
davical or Thunderbird. Can someone tell me what is wrong with the
DURATION values and suggest how I can fix them? I've been using psql to
look at the database, and am willing to use it to make modifications if
necessary.
thanks,
Peter