maemo.org Bugzilla – Bug 7559
Old image displayed as a new one when swiping
Last modified: 2010-08-30 19:43:23 UTC
You need to
before you can comment on or make changes to this bug.
EXACT STEPS LEADING TO PROBLEM:
1. Make some photos.
2. Go to image viewer.
3. Select a random image.
4. Using swipe left and swipe right gestures switch between photos.
New image is displayed after swiping.
Old image is displayed after swiping. After the new image is loaded, it
replaces the old image (without any visual effect). Very rarely old image stays
displayed, even when the new image had loaded.
Created an attachment (id=1892) [details]
Notice the image number: 155/188.
Created an attachment (id=1893) [details]
Notice the image number: 154/188.
Notice that the new image is loading (busy animation).
Notice that the image is the same as the previous one (155/188).
After the swiping there was a visual effect of previous image going off-screen.
This screenshot has been captured after that effect.
Created an attachment (id=1894) [details]
After the new image finished loading
Notice that the image number is the same as on previous screenshot: 154/188.
There is no "busy" animation.
Displayed image is completly different than that on previous screenshot.
Not fixed in 2.2009.51-1.
I confirm this bug.
What is more, sometimes when you swipe back to the previous image you
see the one before that.
E.g, you are in image 145, you swipe right, now you are in 146, now
you swipe left and you end up in 144, not back in 145 as expected.
More precisely: the window title and the details dialog say that
you're watching image 145, but the one that you actually see is 144.
I can reproduce this problem too easily. Just swipe back and forth
once and again and it'll happen.
*** Bug 9429 has been marked as a duplicate of this bug. ***
This has been fixed in package
which is part of the internal build version
(Note: 2009/2010 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
Not fixed in PR1.2. Just harder to reproduce now (old image still can appear
for a very brief moment).