[MeeGo Projects - Bug 9600] New: Nokia phones (N97): *updated* calendar events not accepted by phone
4:06 a.m.
http://bugs.meego.com/show_bug.cgi?id=9600
Summary: Nokia phones (N97): *updated* calendar events not
accepted by phone
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncML
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-syncml-bugs(a)meego.bugs
Estimated Hours: 0.0
Steps to reproduce:
* sync calendar
* update event in Evolution
* sync again
Error encountered:
* bad status ("some changes could not be transferred (local, status 22001)"),
update not transferred to phone
Only occurs for events which contain time zone information. Sending the time
zone information is necessary for recurring events (phone time zone Germany,
event in US: shift from summer to winter time is different).
Originally reported for Nokia 6620 Classic, but also occurs with N97.
Some comments:
* Despite sending with time zone information, the N97 still gets the shift
between summer and winter time wrong:
BEGIN:VCALENDAR
VERSION:1.0
DAYLIGHT;ENCODING=QUOTED-PRINTABLE:TRUE;-07;20110313T100000Z;20101=
107T090000Z;;freeassociation.sourceforge.net;Tzfile;America;Los_An=
geles
BEGIN:VEVENT
TZ:-08:00
LAST-MODIFIED:20101102T104802Z
DCREATED:20101102T103104Z
CLASS:PUBLIC
SUMMARY:Los Angeles
DESCRIPTION:modified - again
DTSTART:20101103T133000Z
RRULE:W1 WE 20101117T143000Z
DTEND:20101103T134000Z
AALARM:20101103T131500Z;;;Los Angeles
DALARM:20101103T131500Z;;;Los Angeles
END:VEVENT
END:VCALENDAR
On 2010-11-02, this occurs at 14:30 German time (+8:00 difference). In the
following weeks, it should occur at 15:30 (+9:00 difference), but the phone
continues to show it at 14:30.
* the phone sends time zone information like this:
BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE;+02;20100328T010000Z;20101031T010000Z;;
BEGIN:VEVENT
SUMMARY:On phone
DTSTART:20101028T060000Z
DTEND:20101028T070000Z
CLASS:PRIVATE
RRULE:W1 TH 20101216T080000
LAST-MODIFIED:20101102T104955Z
PRIORITY:2
END:VEVENT
END:VCALENDAR
Hypothesis: including the zone name and using QUOTED-PRINTABLE breaks parsing
of time zone information, causing both the incorrect displaying of the event
and updating it.
--
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.
4:07 a.m.
New subject: [MeeGo Projects - Bug 9600] Nokia phones (N97): *updated* calendar events not accepted by phone
http://bugs.meego.com/show_bug.cgi?id=9600
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |High
Status|NEW |ASSIGNED
AssignedTo|syncevolution-bugs(a)meego.bu |patrick.ohly(a)intel.com
|gs |
Severity|normal |major
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
5:43 a.m.
New subject: [MeeGo Projects - Bug 9600] Nokia phones (N97): *updated* calendar events not accepted by phone
http://bugs.meego.com/show_bug.cgi?id=9600
ianni67 <ianni(a)ingegneria.unime.it> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ianni(a)ingegneria.unime.it
--- Comment #1 from ianni67 <ianni(a)ingegneria.unime.it> 2010-11-02 05:43:57 PDT ---
I can confirm the bug.
I have a Nokia 6220 Classic and a PC running Ubuntu 10.04.
Using the last available syncevolution version:
SyncEvolution 1.1
using libedataserver-1.2.so.11
using libebook-1.2.so.9
using libecal-1.2.so.7
using libecal-1.2.so.7
using libbluetooth.so.3
If I create an entry with UTC time, sync, and than change the entry from
Evolution (still setting UTC time) and sync again, I get no error and the sync
finishes correctly.
If I create the entry with my local time zone, after a change in the entry I
cannot sync it any more, as I get error 412 or error 22001.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
6:41 a.m.
New subject: [MeeGo Projects - Bug 9600] Nokia phones (N97): *updated* calendar events not accepted by phone
http://bugs.meego.com/show_bug.cgi?id=9600
--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2010-11-02 06:41:32 PDT ---
There's a bug (?) in vtimezone.cpp/ContextToTzDaylight(): it assumes that
t.name is of the format <foo>/<bar> where <foo> and <bar> are
names without
slashes which stand for summer and winter time (CEST/CET).
This is not the case for time zones imported by
platform_timezones.cpp/finalizeSystemZoneDefinitions(). They put the original
TZID into t.name.
This leads to malformed DAYLIGHT properties which have too many components at
the end:
DAYLIGHT;ENCODING=QUOTED-PRINTABLE:TRUE;-07;20110313T100000Z;20101=
107T090000Z;;freeassociation.sourceforge.net;Tzfile;America;Los_An=
geles
Not using any names resolves the original problem (cannot update events), but
might have side effects (perhaps some peers use that information?) and still
leaves one remaining problem:
* recurring events loose the recurrence rules when sent from computer to phone
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
1 a.m.
New subject: [MeeGo Projects - Bug 9600] Nokia phones (N97): *updated* calendar events not accepted by phone
http://bugs.meego.com/show_bug.cgi?id=9600
--- Comment #3 from pohly <patrick.ohly(a)intel.com> 2010-12-13 00:00:04 PST ---
(In reply to comment #2)
There's a bug (?) in vtimezone.cpp/ContextToTzDaylight(): it
assumes that
t.name is of the format <foo>/<bar> where <foo> and <bar> are
names without
slashes which stand for summer and winter time (CEST/CET).
This is not the case for time zones imported by
platform_timezones.cpp/finalizeSystemZoneDefinitions(). They put the original
TZID into t.name.
I've changed libsynthesis to avoid this:
commit 29a7998a0e27d3a664b3ca143baf201b72ecdc6a
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Sun Dec 12 21:36:10 2010 +0100
vtimezone: retain original TZID in imported definitions
VTIMEZONEtoInternal() used to overwrite the original TZID because
there was no other place to store standard and daylight saving TZNAME.
Since there are now explicit fields for that, the code overwriting the
TZID can be removed.
The advantage is that importing and exporting a custom definition
introduces less changes, because now the original TZID will be exported.
commit d9f9af69176d776d09f99d85789973fd5d3b10f4
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Sun Dec 12 21:19:16 2010 +0100
vtimezones: explicitly store std and dst TZNAME
In vCalendar 1.0, the DAYLIGHT property must list standard and daylight
saving zone names, for example CET;CEST.
ContextToTzDaylight() used to extract these two names from the
tz_entry::name field. This was rather implicit and not documented, so
the Linux timezone import code got it wrong and stored the original
TZID (like
/freeassociation.sourceforge.net/Tzfile/Australia/Melbourne), leading
to an invalid DAYLIGHT property with too many components. Such an
entry is accepted by Nokia phones in an ADD, but not an UPDATE
(bugs.meego.com #9600).
The code would also have failed for a (hypothetical) VTTIMEZONE
definition with TZNAMEs that contain slashes.
To make the code more robust and easier to understand, this patch
introduces explicit dstName and stdName fields in
tz_entry. VTIMEZONEtoTZEntry() sets them directly, thus allowing the
removal of two parameters in that function.
ContextToTzDaylight() still falls back to splitting the tz_entry::name
field if dstName or stdName are not set when needed, so these new
fields are strictly optional. In particular the code which creates
tz_entry from the builtin table can work as before.
The code which replaces the original TZID in tz_entry::name with a
combination of its TZNAMEs is still active, although it is no longer
needed. It probably was added in the first place to preserve the two
names so that they can be exported again.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
9:56 a.m.
New subject: [MeeGo Projects - Bug 9600] Nokia phones (N97): *updated* calendar events not accepted by phone
http://bugs.meego.com/show_bug.cgi?id=9600
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #4 from pohly <patrick.ohly(a)intel.com> 2010-12-20 08:56:53 PST ---
I consider the "update" problem as resolved, although Synthesis has not yet
commented on my proposed changes.
The "recurrence" problem was solved by fixing the iCalendar 2.0 -> vCalendar
1.0 conversion in the Synthesis engine (patch by Lukas, bug #11241).
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
1:06 p.m.
New subject: [MeeGo Projects - Bug 9600] Nokia phones (N97): *updated* calendar events not accepted by phone
http://bugs.meego.com/show_bug.cgi?id=9600
--- Comment #5 from pohly <patrick.ohly(a)intel.com> 2010-12-21 12:06:52 PST ---
1.1.0.99.1 is available on syncevolution.org (unstable .deb repos, download
area).
Confirmation that the problem is gone would be nice so that I can release
1.1.1.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
4207
days inactive
4256
days old
syncevolution-issues@syncevolution.org
6 comments
1 participants
participants (1)
-
bugzilla＠meego.com