>>DabaweGNU team report
Now back to the topic at hand, I visited a client the other day and they reported a problem with saving documents in OpenOffice (Writer in particular). This client recently decided to migrate some of their windows PCs to Linux and as expected there are bumps along the way, I will be talking about specific software related issues and how it can be mitigated. This would also serve as reference for future projects where I might encounter the same issue.
When saving a document to a mounted samba share(mounted remote folders) Writer issues an I/O error, creates the file and prevents the user from further saving the document. This issue seems to be isolated in Intrepid Ibex (Ubuntu 8.10) because I don't recall encountering this in Hardy. You can however save the file locally and then drag (copy+paste) the file to the mounted folder, also if the folder is mounted via nautilus the bug does not occur. So naturally that was the work around, the problem was that my client wants to be able to save directly to the remote folder without having to manually mount the share via nautilus (I know what you're thinking...its only a 3 step thing but hey they want it done!). So here is how I temporarily solved the problem ( the permanent fix is to wait for the samba fix to be included in the repos).
- Disable the samba mount definition in /etc/fstab by inserting a hashmark(#) at the start of the definition (this is specific to my client because I had setup the system to automount the samba shares)
- Nautilus like most linux apps accepts commandline parameters so we are going to use that to our advantage simply create a script to automate that.
sudo nano /home/<user_name>/mountshare.sh
Type the following lines
#/bin/sh
nautilus smb://<ip/hostname>/<share_name>
Save the script. - Make the script executable
chmod +x mount_share.sh
- Add an entry to the current session so it is executed on startup. System --> Administration -->Sessions --> Add Entry. Browse and point to /home/
mount_share.sh
Hope this snippet helps those with similar issues...at least until the bug is fixed.