maemo.org Bugzilla – Bug 6017
Clicking the dashboard icon highlights it but does not open the dashboard
Last modified: 2010-03-15 20:53:59 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
1. from the desktop, click on the dashboard icon
dashboard icon turns blue(highlighted), but the dashboard does not open.
i see this at most a couple times a day but haven't yet figured out how to
reproduce it. i will keep trying...
Definitely more information needed, for example how many applications you are
already running (otherwise you will not see the dashboard)... :-)
ok, i've done a bit more testing and i can now reproduce it maybe 1 in 10
it does not matter how many apps are running. if you aren't running any apps,
it will also happen with the application menu icon. furthermore, it may not be
limited to just these buttons. i was able to get the task button in ovi maps to
display the same behavior.
so here are my updated steps:
go to the desktop and use your thumb to touch the dashboard icon (or
application menu icon). when pressing, try to make as much of your thumb
contact the screen as possible. at first the interpreted click may be below the
button so keep moving your thumb up in tiny increments and then try clicking
again. eventually you will get to the point where the button will actually
highlight but by the time you release it will not be registered as a click.
this seems to be the zone that most often causes the bug to occur.
Tried a few times but didn't manage it. :-(
Having a second person confirming this here would be cool.
Created an attachment (id=1535) [details]
stuck dashboard icon
screenshot showing the stuck dashboard icon
Created an attachment (id=1536) [details]
stuck application menu icon
screenshot showing the stuck application menu icon
Just had this happen to me also a little while ago trying to go into
Applications. Second click on the button worked.
This has been fixed in package
which is part of the internal build version
(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
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
(Fix not included in today's 2.2009.51-1 update => updating Version field)
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).