Issue 24304 - Intermittent document saves and goes "Read Only"
Summary: Intermittent document saves and goes "Read Only"
Status: CLOSED WONT_FIX
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: All Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: hennes.rohling
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-12 07:39 UTC by capstone737
Modified: 2004-02-23 11:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description capstone737 2004-01-12 07:39:57 UTC
We have a Windows-Client/Linux-Server network that has neen installed for some
years and that has served our Win2K clients running Office97 very well.

We have recently started using OOo on several of our workstations and have found
an intermittent problem that when OOo is told to save a document, and it saves
OK, but then displays "Read Only" on the blue bar at the top.

The document actually becomes read-only and the user cannot save it again.

If they have typed in addional information to the document, they have to save it
as a new file name and continue working. If they close the document, and then
reopen it, it is no longer read-only. However, the problem may occur again at
any time.

On our network it is a very intermittent problem and it may happen once every
10-20 saves on a document, although it has happened several times in a row to
some users.

It only seems to happen when OOo is told to manually save (click on the FD
icon), and not when it does an autosave. However, this cannot be confirmed.

As the majority of our documents are in Office97 format, the problem occurs when
OOo is saving in MS format. Some users, myself included, have been usung OOo and
saving files in OOo format for some time and we have not noticed it at all.
Thus, the problem may only be relevent to MSO format documents.

We have only noticed it in Calc so far, although it may happen in the other OOo
components too.

I can not find any errors or anything pertinent in the server log files.

It has never occured with Office97 files at all.

The problem has been happening for a few months, but only a few of our users
have been trying OOo so I am unsure how widespread it has become.

Our file server is Red Hat 9 running Samba and it was upgraded to this about the
same time that we started to use OOo so I do not know if the problem was there
with previous Linux/Samba versions.

Current Samba version:

Name        : samba        Relocations: (not relocateable)
Version     : 2.2.7a       Vendor: Red Hat, Inc.
Release     : 8.9.0        Build Date: Sun 06 Apr 2003 14:47:04 EST


smb.conf file:

[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

The file server is only used for file serving/storage. It does not run a print
server etc.


I am now moving the majority of our users to OOo and we are starting to convert
document directories to OOo format. I will continue to monitor the problem and
update this report as information becomes available. Please contact me if you
need any more information.
Comment 1 thorsten.martens 2004-01-12 09:41:52 UTC
TM->HRO: Can you please have a look ? Thanks !
Comment 2 hennes.rohling 2004-01-16 11:43:50 UTC
As reported by mba OOo tries to reopen the file for writing after it was saved
(Saving is done through a copy of the original file). As the whole process is
performed synchronously in one single thread and that saving and reopening the
file (closing it first) is successfull I guess there's a problem with the samba
server configuration. SMB may report the file as still locked for writing within
a cvertain delay.

So I'd suggest to evaluate wether the problem still occurs with disabled kernel
oplocks and if the SMB DOS share mode is well configured.
Comment 3 hennes.rohling 2004-02-23 11:32:13 UTC
Cannot resolve the issue without detailed information.
Comment 4 hennes.rohling 2004-02-23 11:32:35 UTC
Closed.