GNOME Bugzilla – Bug 70569
File dialog incorrectly handles directories starting with a ~
Last modified: 2004-12-22 21:47:04 UTC
I'm trying to change into a directory called ~user, but every time it changes to the user's home directory. Usually this can be addressed by ./~user, but that can have troubles. Steps to reproduce ... 1. $ mkdir foo 2. $ mkdir foo/~user Now to try it: 1. Type in selection textbox: foo/~us 2. Hit tab 3. You're looking at /home/user Or another way: 1. Double-click "foo" 2. Double-click "~user" 3. You're looking at /home/user Here's a workaround: 1. Type in selection textbox: foo 2. Hit tab 3. Type in selection textbox: ./~user (./~us doesn't work) 4. Hit tab 5. You're looking at /home/user/foo/./~user/ (The reason I have a directory called ~user is to stop username enumeration on an Apache server - only one user needs web space.) This is what dpkg says is installed: ii libgtk1.2 1.2.10-9 The GIMP Toolkit set of widgets for X ii libgtk1.2-comm 1.2.10-9 Common files for the GTK+ library pn libgtk1.2-dbg <none> (no description available) ii libgtk1.2-dev 1.2.10-9 Development files for the GIMP Toolkit pn libgtk1.2-doc <none> (no description available)
Thanks for the bug report. I'd agree that it would be nice to catch the case where ~foo actually exists in the current directory, especially when the user clicks on the directory or file name in one of the lists. [ I would suggest that for your particular case, an "Alias" directory in Apache could simplify things. ]
Moving non-critical or hard to fix bugs to 2.0.2
Move open bugs from milestones 2.0.[012] -- > 2.0.3, since 2.0.2 is already out.
Moving a number of non-critical or hard-to-fix bugs to 2.2.0
Moving some hard to fix bugs onto 2.4.0 milestone.
Setting the priority to "Low" for all bugs related to GtkFileSelection. This has been deprecated in favor of GtkFileChooser.
No point putting GtkFileSelection bugs on Future - by the time we get to the future milestone, GtkFileSelection (replaced by GtkFileChooser) will be no longer used anywhere.
*** Bug 155577 has been marked as a duplicate of this bug. ***