maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Incorrect entries in the Birthday Smart Calendar|
|Product:||[Maemo Official Applications] Calendar||Reporter:||stobbsc|
|Status:||RESOLVED FIXED||QA Contact:||calendar-general-bugs|
|Priority:||Low||CC:||adlorenz, andrea, andrew, andre_klapper, christianrol, fraaaaanka, maemo, stobbsc|
SOFTWARE VERSION:1.2009.42-11.203.2 EXACT STEPS LEADING TO PROBLEM: 1. Created a contact on my device 2. Synced with application called Hermes 3. Viewed Birthday Smart calendar 4. Deleted various Contacts from my Contacts DB 5. Viewed Birthday Smart calendar EXPECTED OUTCOME: One Event per contact with a birthday tag should appear in the smart calendar Delete contacts should no longer have event items in the smart calendar ACTUAL OUTCOME: Some contacts had duplicate birthday events in the smart calendar. Some contacts after being deleted still had a birthday even item in the calendar which I would have expected to be removed. REPRODUCIBILITY: Unsure as I can't remove items from the Calendar to start again. EXTRA SOFTWARE INSTALLED:Hermes OTHER COMMENTS: This bug seems to be affect many uses other than myself. It doesn't seem to be related to the Hermes application. As vCards of contacts so 1 birthday event but the calendar shows 2. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/220.127.116.11 Safari/532.0
I've also seen this. I have a single contact who shows up twice for her birthday (7th Dec) in the calendar. Exporting the vCard shows only a single BDAY record.
I had the same problem. Pleas solve this!!!
I noticed that just by removing/reapplyng the birthday calendar from the calendar, keeps creating duplicate events for birthdays.
(In reply to comment #3) > I noticed that just by removing/reapplyng the birthday calendar from the > calendar, keeps creating duplicate events for birthdays. I can confirm this case at least.
And after another deletion & creation of the birthdays calendar my asterisk server now has 3 birthdays. Exporting the entire addressbook shows no duplicates and only one BDAY field in the contact's .vcf Exporting the Birthdays calendar results in this: BEGIN:VCALENDAR VERSION:1.0 BEGIN:VEVENT CREATED:20091215T185014Z SUMMARY:asterisk UID:5 DTSTART:19841215T000000 DTEND:19841215T000000 SEQUENCE:0 STATUS:NEEDS-ACTION LAST-MODIFIED:20091215T185014Z RRULE:FREQ=YEARLY;UNTIL=20371231T235959 END:VEVENT END:VCALENDAR BEGIN:VCALENDAR VERSION:1.0 BEGIN:VEVENT CREATED:20091215T185115Z SUMMARY:asterisk UID:6 DTSTART:19841215T000000 DTEND:19841215T000000 SEQUENCE:0 STATUS:NEEDS-ACTION LAST-MODIFIED:20091215T185115Z RRULE:FREQ=YEARLY;UNTIL=20371231T235959 END:VEVENT END:VCALENDAR BEGIN:VCALENDAR VERSION:1.0 BEGIN:VEVENT CREATED:20091215T185742Z SUMMARY:asterisk UID:7 DTSTART:19841215T000000 DTEND:19841215T000000 SEQUENCE:0 STATUS:NEEDS-ACTION LAST-MODIFIED:20091215T185742Z RRULE:FREQ=YEARLY;UNTIL=20371231T235959 END:VEVENT END:VCALENDAR Note the different UID and timestamp fields. This may be significant: the exported contact contains UID:5, while all other contacts are in the form UID:osso-abook-tmcN.
Running sqlite3 on /home/user/.calendar/calendardb shows: sqlite> SELECT * FROM Components WHERE Summary = "asterisk"; 5|3|4|3|471916800|471916800|asterisk|||1984||2145916799|1|1260903014|1260903014|:Europe/London|0 6|3|4|3|471916800|471916800|asterisk|||1984||2145916799|1|1260903075|1260903075|:Europe/London|0 7|3|4|3|471916800|471916800|asterisk|||1984||2145916799|1|1260903462|1260903462|:Europe/London|0
Thanks for reporting this. This has been fixed in package calendar-backend 0.5-9.8+0m5 which is part of the internal build version 2.2009.42-7 (Note that 2009 is the year and the number after is the week.) A future public update released with or after this build version will include the fix. Note that the fix is NOT included in 1.2009.42-11. Please verify that the new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. Note that Nokia does not announce release dates of public updates in advance.
The problem reported here should be fixed in the update released today for public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes). Please leave a comment if the problem is not fixed for you in this update version.
Confirming, this has been fixed in update version 2.2009.51-1, no more duplicates. If you backed up your calendar data before the update and restored it after, you'll have to create the birthday calendar and delete it the first time. When you recreate it the second time it show no more duplicates.
fixed with update today (
this is now working. I created this bug does that mean I need to close it?
See: Status: RESOLVED Resolution: FIXED and see comment 7.
*** Bug 7958 has been marked as a duplicate of this bug. ***
(In reply to comment #9) > Confirming, this has been fixed in update version 2.2009.51-1, no more > duplicates. If you backed up your calendar data before the update and restored > it after, you'll have to create the birthday calendar and delete it the first > time. When you recreate it the second time it show no more duplicates. > I was about to reopen this report but seen your comment and now I can confirm it is fixed - assuming that user re-created smart calendar, as it seems not fixed at first.