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 332388 - Location bar entries without leading slash behave strangely
Location bar entries without leading slash behave strangely
Status: RESOLVED DUPLICATE of bug 329781
Product: nautilus
Classification: Core
Component: general
2.12.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-23 23:46 UTC by Cameron Harris
Modified: 2006-02-24 09:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Cameron Harris 2006-02-23 23:46:36 UTC
Please describe the problem:
If you enter a location to the location bar in Nautilus without the leading
slash, curious things happen. In particular, the buttons become empty or have
"(null)" in them, and the title bar seems to think you're on another server.

Steps to reproduce:
1. Open a Nautlius file browser window
2. Press Ctrl+L to get the location bar
3. Type "usr/share" or something (no leading slash)



Actual results:
On my system, the title of the window says "share on usr", and there is a blank
button with a folder icon followed by a button that says "(null)".

Expected results:
Either an invalid location dialog or it to display the location as though I had
entered the leading slash.

Does this happen every time?
This is fully reproducable on my system (updated last week, unstable Gentoo) and
a few of my friends with Ubuntu Breezy who claim they're fully up to date.

Other information:
The "share on usr" title seems to indicate that there may be a bit of a
confusion going on between gnome-vfs and nautilus. Also, no filesystem icon
appears at the start of the location bar, making it impossible to get back to /.
Comment 1 Fabio Bonelli 2006-02-24 09:16:37 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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