Red Hat Bugzilla – Bug 154377
File/Open dialog doesn't have a sensible initial directory set
Last modified: 2007-11-30 17:11:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1
Description of problem:
(I think this is a general Gnorm bug, but I observed it in eog, so I'm reporting it there initially)
When you launch eog from nautilus by double-clicking an image file, then in eog you select the File/Open or "File/Open Directory" menu options, the file chooser/selector dialog box always default to the user's home directory, not the directory last used in this dialog, or the directory containing the file currently being viewed.
The file chooser/selector's initial directory should match that of the currently displayed image, since that's where the user will most likely want to open a new image from, or somewhere close to there.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch eog from nautilus by double-clicking an image file not directly in the user's home directory.
2. Select File/Open menu option.
Actual Results: Observer file selector/chooser's initial directory is always set back to the user's home directory.
Expected Results: The file selector/chooser's initial directory should be set to the directory containing the image currently being viewed, or the directory of the last file opened using this method, not the "hard-coded" home-directory location.
Even if Gnome policy is that users always store files in their home-directory, as opposed to system-wide locations, there's still a good chance that the user will be organized and create sub-directories in their home directory. With the current force-home-dir method of the dialog, the user is forced to navigate to the real file location every time they use the dialog.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
This has been fixed in F8, in eog-2.20.1-1.fc8.