To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105224
User andreschnabel changed the following:
What |Old value |New value
================================================================================
Status|RESOLVED |REOPENED
--------------------------------------------------------------------------------
Resolution|WORKSFORME |
--------------------------------------------------------------------------------
------- Additional comments from andreschna...@openoffice.org Fri Oct 9
12:23:03 +0000 2009 -------
reopen.
I also tried a slightly different scentario and the problem is reproducable for
me.
fileserver: samba 3.0.25b on AIX 5.3
client A: MS Win XP, SP3 - MS Word 2002 SP 3
client B: RHEL 4, connected to fileserver using smbmount -o nobrl
OOo 3.1.1 (m19)
Steps:
1. Open word document from Client A
2. Open same Document from Client B
-> Document is opened on both clients
In this sceanrio only Client A (Word) is able to write the file. Client B will
get an I/O error when trying to save (once this happended I am not able to
save the file from Linux side anymore - unless i remount the smb share)
different scenario:
1. Open word document from Client B
2. Open same Document from Client A
-> Document is opened on both clients
Behaviour on save is the same as before.
to compare this with an older version of Ooo I used OOO310m16 on linux side.
1. Open word document from Client A
2. Open same Document from Client B
-> Client B (Linux) correctly reprots that the file is locked
1. Open word document from Client B
2. Open same Document from Client A
-> Client A (Windows) reports the file as invalid (what is not correct, but from
a users POV more save, as it prevents parallel editing and data loss)
Note: in some cases I got a correct lock on the windows side, after a document
was opened from Linux with OOo 3.1.1 - but this rather was the exeptiond and
seemed to happen only after I saved the document from Linux side.
Note: I got the same results when the option "nobrl" was not used on Linux side.
After all we now have three independent sources that confirm the problem. So I'd
assume that there is really something broken. And to me it looks rather like a
general problem with OOo on Linux, not like "happens under rare circumstances
only"
If we can do something to track down the root cause, please tell.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org
For additional commands, e-mail: issues-h...@framework.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
