It appears that this is a well known interaction between OOo 3.0 and
Samba related to file locking. There appears to be a bug here for an
earlier distribution and OOo 3.1 and also issues listed in the OOo
forums and buglists. It can cause a crash on load or it can cause
unspecific 'general IO errors' when trying to save an edited file. I had
this happen with an HTML file which I was able to load then 'save as'
but not save when changed.

Some of the workarounds suggested have been to reset some configuration
scripts or disable file locking in the soffice script or to use the
'nounix' option in the CIFS mount or to regress to an smbfs mount. (I
tried the script refresh and it didn't do the job so I am now in the
process of testing the 'nounix' option)

It does appear that mounting the share via 'Nautilus->places->network'
may not express the problem. That mounts as "gvfs-fuse-daemon on
/home/username/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=username)" rather than "//server/share on
/lan/server/share type cifs (rw,mand)" - I don't know that much about
how the gvfs-fuse-daemon mounts things (yet) to understand how it's
mounts of SMB shares differs from CIFS but that difference may yield
some insight into this problem. (I might try some of thoe gvfs options
in autofs as well, to see if I can find one that will make a difference)

I'll see if I can get a backtrace - that process looks to be a pain but
I understand the need; may take a while.

In regard to the test indicated, I think the key is opening, editing,
and saving an existing file rather than just creating a new one. It does
appear to be a multi faceted issue and I don't think it is anything as
simple as file specific. That makes it rather tough to track down.

-- 
crashes opening network file, leaves lock file
https://bugs.launchpad.net/bugs/578402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to