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 169213 - Path bar needs to update if a path component is renamed
Path bar needs to update if a path component is renamed
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
unspecified
Other Linux
: Normal normal
: Small fix
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 320247 filechooser-nautilus
 
 
Reported: 2005-03-04 17:45 UTC by Vincent Noel
Modified: 2018-04-15 00:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vincent Noel 2005-03-04 17:45:40 UTC 
In a file chooser :

* enter a folder on your desktop
* with nautilus, rename a folder on your desktop
* go up one level in the file chooser
* the new folder name appear in the list, along with the old one

This may be related to bug #166317.
Comment 1 Vincent Noel 2005-03-04 17:46:17 UTC 
Also, when this happens you cannot navigate the folders structure anymore. You
have to close and reopen the file chooser.
Comment 2 Matthias Clasen 2005-04-08 14:07:32 UTC 
I don't see both folder in the file list, I do see the old name in the path bar,
however, and the button doesn't work.
Comment 3 Vincent Noel 2005-04-08 14:20:11 UTC 
Yeah, you're right, the behavior is now the one you describe.
Comment #1 is not relevant anymore either.
Comment 4 Federico Mena Quintero 2005-04-28 23:47:34 UTC 
Retitling for clarity
Comment 5 Timothy Arceri 2013-06-14 10:52:46 UTC 

*** This bug has been marked as a duplicate of bug 320247 ***
Comment 6 Timothy Arceri 2013-06-24 04:21:00 UTC 
Reopening and marking as blocker instead
Comment 7 Matthias Clasen 2018-02-10 05:00:47 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 8 Matthias Clasen 2018-04-15 00:13:01 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new