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 627007 - Location bar still showing previous directory after having deleted it
Location bar still showing previous directory after having deleted it
Status: RESOLVED DUPLICATE of bug 310205
Product: nautilus
Classification: Core
Component: Location Bar
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-16 01:41 UTC by ali
Modified: 2010-08-20 10:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ali 2010-08-16 01:41:26 UTC 
The new location bar, that shows the visited folders in tabs has a bug. For example, suppose you go to the directory 

"/home/user/Desktop/somefolder" The Location bar has the tabs "home", "user", "Desktop", and "somefolder". The active tab is "somefolder".

Now you press the "Back" button and you go to the "/home/user/Desktop" directory. 
The Location bar still shows the same 4 tabs but now the active tab is "Desktop". This is OK so far.

Now you DELETE the directory "somefolder", and you expect the fourth tab "somefolder" to also disappear but IT STAYS. If you click on it you get an error message of course.


Expected Results: When you delete a directory you have previously visited, its tab should also disappear from the Location bar simultaneously with the deletion.
Comment 1 André Klapper 2010-08-19 10:33:49 UTC 
Which Nautilus version is this about?
Comment 2 ali 2010-08-19 16:53:15 UTC 
2.30.1
Comment 3 Cosimo Cecchi 2010-08-20 10:27:01 UTC 
This should have been fixed with bug 310205.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 310205 ***