Description of problem:
When using the "places" "connect to server" application there are some weird
problems. I can mount a location with a share, browse the folder structure and
open the files, but I can not save or copy files. This is in evolution, open
office, vim etc. What I can do however is use open office, browse to the share
and file and open it, and then I can write to it.
Version-Release number of selected component (if applicable):
Windows 2000 server
Windows 2000 Directory Services
Userid on local system is local credentials
Userid on Windows 2000 Server is directory services userid.
Use connect to places to connect to a windows 2000/2003 or netapp cifs system,
input userid, domain name and password credentials.
It will give an error message;
The specified location is not mounted.
Close this error box and go to the shortcut on the desktop.
Open the share, and browse to an open office doc file type, and open with open
Edit and save.
Error will pop up saying
Error saving the document $documentname
General input/ouput error while accessing /home/$username/.gvfs/$sharename on
Press ok, and error will come up again.
Press ok, and new error comes up;
Error saving the document $filename
General input/output error.
Back on the desktop a second shortcut of the share is now on the system.
Open up open office, use file open dialog and browse to file location.
Opening the file will request a password prompt; (open office dialog, not gnome)
Please enter user name and password for "$domainname" on $servername here.
Remember password till end of session.
Replace guest with the previously entered userid and password, that was used in
the "connect to server" application.
Document opens, edit document and press save.
Sorry I forgot to note:
Did not have the normal $servername/$sharename/$foldername. It was as above. I
just dont know if that is the expected behaviour, typically the unc requires
- Openoffice uses different method accessing SMB shares.
- "The specified location is not mounted" error from Places menu is a known
- overall gvfsd-smb has many issues at the moment which are being worked on
Could you please install new gvfs version from testing repository
(https://admin.fedoraproject.org/updates/F9/FEDORA-2008-5197) and attach the
debug log from "/usr/libexec/gvfsd -r" here? It would help us to determine the
real cause of the errors you got.
I can send the information but there is a lot of name resolution, and other
items I would not feel comfortable putting on the internet. Is there an easy way
to clean the data that would still be useful to you>
I see, that's the part of smb debugging output. You can replace all adresses
with xxx.xxx.xxx or something like that. Passwords should not be exposed at any
Created attachment 311101 [details]
Output as requested
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.