https://bugs.meego.com/show_bug.cgi?id=1133 --- Comment #1 from ovek <ovek(a)debian.org&gt; 2011-06-19 18:20:23 UTC --- Just going to update this report by saying that this behaviour isn't accidental - it was a part of the design from the start. The program's only knowledge of the sync time was meant to be the sync job itself, which is stored in the N900's alarm database. If you disable the job, then the alarm is removed and, with it, any knowledge of the previous sync time. To enable the job again, a new time has to be set, and the default happens to be the current system time. It may be a valid issue, so I don't think I should close this bug, but I'm not likely to change this anytime soon. Unless, I suppose, someone makes a decent patch. -------- Product: SyncEvolution Component: Maemo 5 MeeGo Release: unspecified Severity: trivial Priority: Undecided Keywords: Status: ASSIGNED Who: ovek(a)debian.org Assigned To: ovek(a)debian.org Target Build: --- Flags: Changed: -------- https://bugs.meego.com/show_bug.cgi?id=1133 -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.