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 631908 - Open File dialog results in wrong file opened
Open File dialog results in wrong file opened
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2010-10-11 17:49 UTC by Tristan Moody
Modified: 2011-06-15 00:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tristan Moody 2010-10-11 17:49:02 UTC
Bug also filed for Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/558674

When using the file-open dialog in any of several different programs (Firefox seems to be the primary location, though this behavior has also been noted in Google Chrome and OpenOffice), the file actually opened is not the one selected.  

This problem does not seem to occur if the filename is directly typed in, rather than clicked upon.

Additionally, when choosing a file to open, the file-open dialog appears unresponsive to subsequent selections after the first file is selected (i.e., the highlighted file will not change).  Clicking open then opens a completely unpredictable file.  

This seems to happen mostly in directories containing a large number of files.
Comment 1 André Klapper 2010-10-24 17:44:06 UTC
Does this still happen in gtk 2.22?

I have never seen this in 2.20 myself... Exact steps welcome, especially what other file is opened instead (one before? one after? random?)
Comment 2 Tristan Moody 2010-10-25 00:21:18 UTC
Not sure about 2.22--will have to test it.  I'll try to post a screencap when I can get on my linux machine next (tomorrow hopefully).  The file ultimately selected is usually about three or four lines above the intended file, but it is not at all predictable.  I've been trying to capture this behavior in gdb, but I apparently can't get a breakpoint set properly.  Again, this only seems to happen when there are somewhere around a hundred or more files in the working directory.
Comment 3 Tristan Moody 2010-10-27 16:01:20 UTC
It does not appear to happen in 2.22.  Additionally, the sluggishness/unresponsiveness mentioned in the OP does not appear to occur either.
Comment 4 Matthew Wild 2011-06-15 00:45:45 UTC
Hi Tristan, mind sharing whereabouts you were hunting for the bug, and how you were trying to debug it? I'm no stranger to gdb, but debugging GTK is not my speciality :)

It's good news that this is resolved in 2.22, but Ubuntu 10.04 LTS ships with 2.20 and is supported for a couple more years. It would be good for me and a whole lot of other people if we could nail this down before then, assuming that's possible - it's a most annoying issue (that looks, probably deceptively, like it should have a simple answer).