maemo.org Bugzilla – Bug 5593
Contacts re-appear in list after disabling and re-enabling accounts
Last modified: 2010-03-02 23:28:13 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: 1.2009.41-10 STEPS TO REPRODUCE THE PROBLEM: 1. Enable Skype account (#1) 2. Merge a Skype username for account #1 in the contact list to another contact (e.g. merge the john1978 to the John Smith contact) 3. Disable Skype account #1 4. Enable another Skype account (#2) 5. Disable account #2 6. Enable account #1 again I guess it is the some for other types of accounts, but I encountered it with a Skype account. EXPECTED OUTCOME: The account name does not appear in the main list, but is hidden, since it is already attached to a contact. ACTUAL OUTCOME: The account name appears again in the main list of contacts, as well as under the contact's details. REPRODUCIBILITY: always EXTRA SOFTWARE INSTALLED: OTHER COMMENTS: User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.0.14) Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14
Known problem, must fix.
Correction: it's actually fixed, coming in a future update.
Fixed in internal week 42 build. Any public update released with or after this build version (x.2009.42-y) will include the fix. 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.
(In reply to comment #3) > Any public update released with or after this build version (x.2009.42-y) will > include the fix. Correction: the 1.2009.* builds will most likely not include it.
Please note that the fix for this issue is NOT included in the final Maemo5 version 1.2009.42-11 that was released today. The fix will be included in the next update after 1.2009.42-11.
*** Bug 6426 has been marked as a duplicate of this bug. ***
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.
I can confirm it is fixed.