[Syncevolution-issues] [MeeGo Projects - Bug 10091] Sony Ericsson t700 crashes with VALARM section in .ics
http://bugs.meego.com/show_bug.cgi?id=10091
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |High
Status|NEW |ASSIGNED
CC| |patrick.ohly(a)intel.com
AssignedTo|syncevolution-bugs(a)meego.bu |patrick.ohly(a)intel.com
|gs |
Target Milestone|--- |1.1.1
--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2010-11-16 23:33:54 PST ---
(In reply to comment #6)
i could narrow the bug down:
Excellent!
the problem seems to be in the valarmtrigger atribute. While a direct
time
value works with my SE t700:
BEGIN:VALARM
X-EVOLUTION-ALARM-UID:20101104T235022Z-14632-1000-1-5@ThinkPad-T61
DESCRIPTION:Arbeit
ACTION:DISPLAY
TRIGGER;VALUE=DATE-TIME:20101117T064500Z
END:VALARM
it doesnt if the trigger is related to the event (the way evolution handles
alarms of events), then it crashes:
BEGIN:VALARM
X-EVOLUTION-ALARM-UID:20101104T235022Z-14632-1000-1-5@ThinkPad-T61
DESCRIPTION:Arbeit
ACTION:DISPLAY
TRIGGER;VALUE=DURATION;RELATED=START:-PT1H
END:VALARM
Nokia phones had similar issues (bug #1657). The solution was the
alarmTimeToUTC=TRUE part of
/usr/share/syncevolution/xml/remoterules/server/00_nokia.xml.
Can you try with the following file in your home directory?
~/.config/syncevolution-xml/remoterules/server/00_sony_ericsson.xml
----------------> snip <----------------------
<remoterule name="SonyEricsson">
<!-- defaults for *all* Sony Ericsson phones; can be overridden for
specific models later on -->
<manufacturer>SonyEricsson</manufacturer>
<finalrule>no</finalrule>
<!-- At least the Sony Ericsson T700 is only able to deal with alarm
times in UTC,
but rejects relative times. BMC #10091 -->
<rulescript><![CDATA[
alarmTimeToUTC = TRUE;
]]></rulescript>
</remoterule>
----------------> snip <----------------------
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.