I have done some more testing: 1. I started Windows XP on one of the clients and set up a shared folder there. I could access this folder from Intrepid OpenOffice and I could save without any problems. Also it didn't ask for an extra password like described in Step 7 above. It just did what it should do.
2. Then I set up a share on my main workstation (running a pretty fresh Ubuntu 8.04) with the Nautilus tools (sudo nautilus, because it wont' work as normal user, rightklick folder, select "Sharing Options"). It even had to install the necessary packages, there was no sambaserver running on this machine before. 2a. I started Win XP, connected to the new share and created a file - no problem. 2b. I switched to my Intrepid machine, opened the file, changed it, saved it, no problem. 2c. I rebooted the Intrepid machine, started OOo writer, typed, tried saving to the share and it failed again. 2d. I closed OOo Writer, reopened it, typed, saved to share and worked again. I opened a second doc and it worked too. 2e. Then I closed OOo and waited for >30 minutes. Started OOo, created file, saved, still no problem. 2f. Then I logged out (but did not restart), logged back in, started OOo, and the problem is there again. And if I close OOo and reopen it, it works again. To sum up: 1. Windows share - all clients work, XP, Hardy and current Intrepid 2. Debian Etch share + Hardy share - Windows client works, Hardy client works, Intrepid fails (on first access, subsequently OOo succeeds). So, interestingly, I could use Windows as server and Linux as client (ugh...). The problem only shows up when I try to use OOo on an Intrepid machine connecting to a Linux SMB server (Etch or Hardy). The problem only shows up the first time I try to save to a share. Closing OOo, reopening it solves the problem, from then I can save files without problems. Also I don't get asked for a password again. I am not a programmer but could it be that OOo somehow a. does not accept GVFS permissions, b. asks for a password itself c. fails anyway, but d. keeps the authorization for the share alive so that subsequent writes to the shares succeed? Most importantly: Is this thing reproducible for others? I will help with whatever resourced I have. Regards, Christian -- openoffice cannot write to samba shares (some kind of gvfs timeout?) https://bugs.launchpad.net/bugs/279789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
