maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Unable to set a Google Talk account to Away|
|Product:||[Maemo Official Applications] Chat & Call & SMS||Reporter:||crolix|
|Status:||VERIFIED FIXED||QA Contact:||presence-bugs|
|Priority:||Low||CC:||andre_klapper, crolix, mikhail.zabaluev|
SOFTWARE VERSION: 1.2009.42-11 EXACT STEPS LEADING TO PROBLEM: 1. Open the status menu and select "Availability". 2. Select "New status". 3. Tap on a Google Talk account to select a status for it. EXPECTED OUTCOME: The displayed list contains the following values: Available, Away, Busy, Sign out. ACTUAL OUTCOME: The displayed list contains the following values: Available, Busy, Sign out. REPRODUCIBILITY: Always. OTHER COMMENTS: The above works correctly for a Skype account. If a Skype account is selected in the steps above instead of a Google Talk account, the following values are shown: Online, Away, Do not disturb, Invisible, Offline.
This is currently being worked on.
This has been fixed in package rtcom-accounts-ui 4.117-1+0m5 which is part of the internal build version 2009.53-2 (Note: 2009 is the year, and the number after is the week.) A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.) Please verify that this 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. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
The bug is still there after the 3.2010.02-8 update.
Perhaps I reopened this bug too hastily. The rtcom-accounts-ui does not seem to be included in the 3.2010.02-8 update, so this bug can't be verified yet. Setting back to fixed...
As written in comment 3 already: "This is not always already the next public update."
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).
Works in 10.2010.19-1.