After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 660877 - Wrong preview image in the file open dialog.
Wrong preview image in the file open dialog.
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
filechooser-harder-fix
: 619695 740991 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-10-04 14:01 UTC by Pedro Villavicencio
Modified: 2017-08-15 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2


Description Pedro Villavicencio 2011-10-04 14:01:07 UTC 
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/864494

"Hello,
File open dialog seems to display wrong preview image in some cases.
Please study this video:
http://www.futuredesktop.com/tmp/file-open-test.ogv

You can reproduce this issue with:
1) Open the program for change-desktop-background (appearance dialog).

2) Click the [+] button and browse to Test/ images.

3) In the file open dialog, press "b" letter to browse just the images that start with "b". This is important, ok?

4) Now use arrow-keys to move from one bimage* to another. The preview image is wrong.

Notice: I could only produce this when I restricted the search with a letter or word, and then used ARROW-KEYS to jump to next/previous file. Selection with mouse works always right.

Here are the actual Test/ images:
http://www.futuredesktop.com/tmp/Test.tar.gz"
Comment 1 Timothy Arceri 2013-02-09 11:27:43 UTC 
I think this may be some sort of issue with the typeahead functionality of GTKTreeView not setting the selection correctly. Or maybe a conflict between the typeahead functionality and the handling of selections in filechooser.
Comment 2 André Klapper 2013-08-25 09:44:20 UTC 
Might be a duplicate of bug 619695?
Comment 3 Matthias Clasen 2014-12-08 11:46:12 UTC 
i can't directly follow the ubuntu-specific reproduction instructions here, but I believe this was recently fixed by f678e48a08a376cbed060b52cd9746febf44c6cc
Comment 4 Daniel Boles 2017-08-15 20:07:17 UTC 
*** Bug 740991 has been marked as a duplicate of this bug. ***
Comment 5 Daniel Boles 2017-08-15 20:07:22 UTC 
*** Bug 619695 has been marked as a duplicate of this bug. ***