Red Hat Bugzilla – Bug 187019
"Save As" dialog tries to access samba bookmarks of nautilus
Last modified: 2008-05-06 11:40:25 EDT
Description of problem:
After add a bookmark to a samba share in nautilus, all gnome "Save as" dialog
will try to access the samba directory. This makes open a "Save as" dialog
Even worse, if the samba share requires a password, the "Save as" dialog will
not show, and instead gnome asks for the keyring password. It made me astounded
that openoffice and archive-manage keeps asking me for the keyring password when
I just want to save/extract a local file! And I suspected if my newly installed
FC5 had been affected by some trojan horses.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a samba share in nautilus bookmark, and save the password to the samba
share in the keyring.
2. Create a new file in openoffice writer, then click "save" button.
Openoffice will ask the keyring password. And the save dialog will not show
until you have inputed the password.
"Save as" dialog should not try to samba share!
That is a gtk+ dialog.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.