Please note that I have spent a lot of time researching this and I believe that
it is a bug.


***** It is an INTERMITTENT problem and happens about 10%-20% of the time ***** 

We have 30 x Win2k workstations running OOo and connected to a RH9 file server
via Samba.

When we create a new document in OOo (have only tried Calc and Writer) and save
it for the first time it, it saves OK but then gets write protected so it cannot
be saved to again. The document name appears on the blue window bar with "Read
Only" after it. If you wish to continuing editing the document and save changes,
you have to close it and then re-open it again. Often it opens in Read Only mode
again and you have to close it and try again. Sometimes you have to repeat this
several times until it opens in R/W mode. It is quite intermittent though.

Then, if you save it again it may well go back to Read Only mode again. This is
quite intermittent and only happens 10-20% of the time.

The same thing happens with existing documents, but it is similarly
intermittent. We only save and retrieve documents from our file server and so I
do not know if it happens on a local hard drive.

On nearly all of our Windows PCs, we have Office 97 installed along with OOo and
we have no problems with Word or Excel.

It *seems* to happen more with Calc than Writer, but that may be related to the
more widely used application that the users are using.

I have looked through the Samba logs on the server at /var/log/samba and there
is nothing there that hightlghts a problem at all.

When it "auto-saves" the problem doesn't seem to appear, and it is only when you
manually save by clicking on the floppy disk "Save Document" icon that the
problem appears.


The Linux kernel version:
2.4.20-8

The Samba version:
Name        : samba
Version     : 2.2.7a
Release     : 8.9.0


Samba smb.conf:

[global]
        workgroup = workgroup
        server string = Samba Server
        log level = 2
        log file = /var/log/samba/log.%m
        max log size = 2000
                                                                               
                                             
        # Browsing election options
        os level = 34
        local master = yes


[Shared]
        comment = Shared Directories
        path = /home/Shared
        valid users = @users
        writable = true
        force group = users
        force directory mode = 770
        inherit permissions = yes
 
Because of the frustration of trying to work with documents while this problrm
exists, some of our users are refusing to use OOo and have gone back to MSO97
and have no problems.

I have installed the 2.4.20-24.9 kernel, but haven't been able to easliy reboot
as the system is in use 24 hours per day, and we are behind a firewall.

Uptime:
14:24:00  up 81 days, 18:54

If you feel that the newer kernel would be worth trying, I can formally schedule
a reboot and we can try it again.

If you need any extra information, please let me know.