[Bug 20916] New: [Dapper] Image collection: odd display glitch on some pics

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=20916
Ubuntu | eog

           Summary: [Dapper] Image collection: odd display glitch on some
                    pics
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: eog
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: vincent.trouilliez at modulonet.fr
         QAContact: desktop-bugs at lists.ubuntu.com


I tried the "image collection" feature of eog, and notice something strange when
I click on some pics.
MOst of the time, when I click on a pic from lower part of the window, it is
displayed cleanly and instantly in the upper part of the window, as you would
expect. However when I click on some pics of the collection, something strange
happens. I attached two little pics that illustrate this problem. One is
displayed cleanly, "B.jpg", and "A.jpg" show the problem.

1) Put these two pics say on your desktop, alone, and open with eog.
2) press "F9" to display the image collection at the bootom of the window
3) enlarge the main window etc, so that eog don't have to scale down the pics.

4) click on B.jpg, it is displayed cleanly and instantly.
5) now clik on A.jpg and pay attention: during nearly a second, the picture
"moves" up and down by about say a couple pixels each way, and so does the
widget that splits the eog window in two halves.
6) once B.jpg has finished "dancing", A.jpg is eventually displayed, fast and
cleanly.

It only does it when B is displayed and you click on A, not the other way around.

It looks very untidy and really gets in the way, so if I can do anything to help
trouble-shoot it, just ask...

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.