Open and Save dialogs descends down into sub directory if the selected directory has one sub directory

Bug #1102042 reported by Daniel Aleksandersen
118
This bug affects 48 people
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Medium
gtk+3.0 (Ubuntu)
Fix Released
Low
Unassigned
Precise
Won't Fix
Low
Unassigned
Quantal
Won't Fix
Low
Unassigned
Raring
Won't Fix
Low
Unassigned

Bug Description

When selecting a directory that has one sub-directory, the open dialog descends down into the sub-directory.

1. Make this exact folder structure: ~/a-dir/b-dir/ (only one sub-directory in a-dir, a-dir can have files)
2. Open the Open dialog and double-click on the a-dir in your Home folder and click Open

I expect the a-dir to be selected, but b-dir is selected in stead. In the attached video you can see the a-dir being open, but the selection clearly uses b-dir instead.

3. Reopen the Open dialog and double-click on the a-dir
4. Type ./ in the Open dialog’s location field

The input in the edit field is automatically changed to ./a-dir/b-dir/. The only way I have found to actually select the a-dir is to press backspace once after completing step 4.

Similar behavior can be seen in the simplified dialog (e.g. when selecting destination for newly opened torrent files in Transmission).

Ubuntu 12.10. Programs affected gedit, transmission, gnome-screenshot, others.

Tags: quantal
Revision history for this message
Daniel Aleksandersen (da2x) wrote :
summary: - Open dialog descends down into sub directory if the selected directory
- has exactly one sub-directory
+ Open and Save dialogs descends down into sub directory if the selected
+ directory has one sub directory
Revision history for this message
Daniel Aleksandersen (da2x) wrote :

You can also notice that the suggestions that appear when I type dot in the attached video is for the Home directory and not the a-dir.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

affects: gtk+3.0 (Ubuntu) → ubuntu
Changed in ubuntu:
importance: Undecided → Low
status: New → Confirmed
affects: ubuntu → gtk+3.0 (Ubuntu)
Changed in gtk:
importance: Unknown → Medium
status: Unknown → New
Changed in gtk:
status: New → In Progress
Changed in gtk:
status: In Progress → Fix Released
Changed in gtk+3.0 (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+3.0 - 3.8.2-3ubuntu2

---------------
gtk+3.0 (3.8.2-3ubuntu2) saucy; urgency=low

  * Use simply expanded variable to avoid FTBFS due to recursive reference of
    CFLAGS on armhf.
 -- Iain Lane <email address hidden> Mon, 08 Jul 2013 17:32:34 +0100

Changed in gtk+3.0 (Ubuntu):
status: Fix Committed → Fix Released
Jeremy Bícha (jbicha)
Changed in gtk+3.0 (Ubuntu Raring):
importance: Undecided → Low
status: New → Triaged
Changed in gtk+3.0 (Ubuntu Quantal):
status: New → Triaged
importance: Undecided → Low
Changed in gtk+3.0 (Ubuntu Precise):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in gtk+3.0 (Ubuntu Quantal):
status: Triaged → Won't Fix
Revision history for this message
Rolf Leggewie (r0lf) wrote :

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".

Changed in gtk+3.0 (Ubuntu Raring):
status: Triaged → Won't Fix
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in gtk+3.0 (Ubuntu Precise):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.