http://bugzilla.moblin.org/show_bug.cgi?id=10489
Summary: Tasks lose alarm details on way from N900 to
evolution (HTTP server)
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Generic
OS/Version: Moblin Linux
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected]
Client: N900 syncevolution 0.9.2
Server: Desktop syncevolution compiled using 1.0beta2 source code
Evolution 2.26.1
Scratchbox in use for emulating N900 - using maemo 5 binary release from Mar 22
1) create new task on the N900 call it "n900 test alarm task"
check the alarm box
select 9am and confirm
click save
2) Sync (I am using syncevolution-frontend version 0.5)
3) Confirm the task appears in evolution on the desktop
If evolution is already running, you may need to change
views (say changing to mail then back to tasks)
in order for the new info to appear
4) Modify the title of the task in evolution
NOTE: that start date and end date
are as expected BUT the time of BOTH is 12:00AM
Expected would be the time of the Alarm
Examining the local evolution calendar file we see
that the start/stop time is not "right" and no state info on the alarm
(I don't know off hand if ical supports storing this info such as
as alarm state on/off)
BEGIN:VTODO
DTSTAMP:20100420T202906Z
CREATED:20100420T202906Z
UID:32
SEQUENCE:0
SUMMARY:n900 test task alarm time bug
DESCRIPTION:n900 test task alarm time bug
DTSTART:20100420T000000
DUE:20100420T000000
STATUS:NEEDS-ACTION
LAST-MODIFIED:20100420T202906Z
END:VTODO
IN addition, if you modify the title on the desktop and re-sync with N900
you will find the task no longer has an alarm (the checkbox is now unchecked)
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
