http://bugs.meego.com/show_bug.cgi?id=10131
Summary: EXDATE ignored by SonyEricsson t700 calendar
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - (e.g.:
meego-netbook-ia32-1.0.90.0.20100831.1)):
HARDWARE MODEL (on what HW this bug is uncovered): T700
BUG DETAILED DESCRIPTIONS
===========================================================
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
===========================================================
1.create reoccuring event (due to bug 10092 without the "until" option, either
indefinitly or repeated n times) with evolution or mobile phone
2.add exeption to one of the events (only works in evolution)
3.sync
EXPECTED OUTCOME:
===================
SE should handle the event correctly: at date of exeption, there should be no
event in the calendar
ACTUAL OUTCOME:
===================
SE ignores the EXDATE values in the ics file: the event shows up at all dates,
even on the specified exeptions
USER IMPACT:
===================
usability to view a calendar on SE gets very low, lots of events are
reoccuring, and the exeptions are often the most important part of it.
REPRODUCIBILITY:
(always, less than 1/10, 5/10, 9/10)
=====================================
always
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:
===================
The only solution i could think of was to split up the n-repeated event into n
different events so SE could view them correctly.
--
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.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
