maemo.org Bugzilla – Bug 5415
Contact widgets move to active desktop after merge
Last modified: 2010-01-14 12:45:09 UTC
You need to
before you can comment on or make changes to this bug.
(Control Panel > General > About product)
STEPS TO REPRODUCE THE PROBLEM:
1. Add a contact to a desktop
2. Switch to a different desktop
3. Merge another contact to the contact whose widget is on the desktop
Contacts are merged and the widget remains on the desktop it was placed on.
Contacts are merged and the widget moves to the desktop active while merging.
EXTRA SOFTWARE INSTALLED:
User-Agent: Mozilla/5.0 (X11; U; Linux armv7l; en-GB; rv:1.9.2a1pre)
Gecko/20090928 Firefox/3.5 Maemo Browser 188.8.131.52 RX-51 N900
(In reply to comment #0)
> 3. Merge another contact to the contact whose widget is on the desktop
What are the exact steps to do this?
3. Merge another contact to the contact whose widget is on the desktop:
3.1 Open the Contacts application
3.2 Select the contact thas has a desktop widget
3.3 Select 'Merge contact' from the menu
3.4 Select any other contact to be merged with the selected contact
I can confirm this bug. After merging a contact, I noticed that contact
switched from the desktop I had originally placed it on to the current desktop.
Confirming as per second comment. Thanks for clarifying the steps!
i can also confirm this bug. and finally i understand why my desktop repeatedly
got so mixed up, thanks! :)
This has been fixed in package
which is part of the internal build version
(Note that 2009 is the year and the number after is the week.)
Any public update released with or after this build version will include the
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.
*** Bug 6941 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
This is VERIFIED, the fix works well.