---- Reported by juergenoschumacher@gmx.de 2010-10-21 09:15:24 +0000 ---- HARDWARE MODEL (on what HW this bug is uncovered): Ubuntu Linux 10.04, memotoo.com, Nokia N900 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. Evolution calender got out of sync; Evolution calender entries were all doubled after a slow sinc 2. Deleted the calender on the server side at memotoo 3. Deleted the calender in Evolution 4. Restored the calender in Evolution from a backup 5. Performed a new sync with the server at memotoo 6. Most of the entries after the clock change on 31st of October appear to be shifted by one hour backwards in Evolution EXPECTED OUTCOME: Correct handling of time-zones while sincronizing =================== ACTUAL OUTCOME: =================== USER IMPACT: =================== REPRODUCIBILITY: (always, less than 1/10, 5/10, 9/10) ===================================== EXTRA SOFTWARE INSTALLED: ============================ OTHER COMMENTS: =================== ---- Additional Comments From patrick.ohly@gmx.de 2010-12-15 02:22:02 +0000 ---- When you say "Evolution Calendar", you mean the calendar on the N900? I am asking because that calendar is not stored in Evolution Data Server; it's some Nokia proprietary storage. After you restored your data in that calendar (step 4), did clean the data on the server or use a "refresh-from-client" sync? It is not obvious what kind of sync was executed in step 5 (two-way, slow, refresh) and what kind of data was sent back and forth. Can you reproduce the problem, perhaps with some simple test data, and run the sync with loglevel=4 in the ~/.config/syncevolution config (grep for that property)? Then attach the log file here or (if it contains confidential data) send it via email. It could also be that this is caused by the calendar storage deficiency mentioned in https://bugs.meego.com/show_bug.cgi?id=6680. A log would show that. --- Bug imported by patrick.ohly@gmx.de 2012-08-19 20:56 UTC --- This bug was previously known as _bug_ 8761 at https://bugs.meego.com/show_bug.cgi?id=8761 Unknown platform unknown. Setting to default platform "". Unknown operating system unknown. Setting to default OS "".
I'm not completely sure it's the same bug, but it might. I'm using the following components: - laptop running evolution 3.6.3 - Nokia N9 phone I'm sync'ing using syncevolution 1.3.2. Since the daylight saving switch, all the “all day” events are off by 2h when syncing: - when created on the laptop as a 24h event on apr 4, they appear on the phone as starting apr 4 at 02:00 and ending 24h later - when created on the phone as a 24h even on apr4, they appear on the laptop as starting apr 3 at 22:00 and ending 24h later It's pretty annoying, especially since it's quite sure nothing will change on the N9…
(In reply to comment #1) > I'm not completely sure it's the same bug, but it might. > > I'm using the following components: > > - laptop running evolution 3.6.3 > - Nokia N9 phone > > I'm sync'ing using syncevolution 1.3.2. Since the daylight saving switch, > all the “all day” events are off by 2h when syncing: > > - when created on the laptop as a 24h event on apr 4, they appear on the > phone as starting apr 4 at 02:00 and ending 24h later > - when created on the phone as a 24h even on apr4, they appear on the laptop > as starting apr 3 at 22:00 and ending 24h later Please increase the loglevel property to 4 in your sync config on the laptop, run a sync with test data where these two cases happen (ideally with clearly marked subject tests), then attach the compressed syncevolution-log.html file here. If you changed nothing else, no confidential data will be in the log. If unsure, then search for just the data conversion parts involving the test data and cut-and-paste that here as plain text. Unfold the entire log first (++ characters at the top of the file).
Is there still interest in fixing this?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/122.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.