Issue 109014 - OpenOffice Crashes when saving a file to a network drive
Summary: OpenOffice Crashes when saving a file to a network drive
Status: CLOSED DUPLICATE of issue 107192
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO310m19
Hardware: PC (x86_64) Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-06 18:14 UTC by grelarse
Modified: 2010-03-04 18:39 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description grelarse 2010-02-06 18:14:54 UTC 
1.  Version is 00310m21, but this was not a choice in the menu.

2.  I open existing writer or calc documents saved on a NAS on my home network.
 I make a change and then try to save.  OpenOffice crashes immediately, with no
warning and no possibility to send a crash report.  If I restart Office, open
the same document, and then try to save on my local disk, the file is saved
successfully.

I've been using OO successfully for several weeks after installing from SuSE
with the 11.2 SuSE release. This suddenly started happening today.  I'm not
aware of any change that could have caused this
Comment 1 grelarse 2010-02-06 18:21:05 UTC 
Strangly, if I open the file that I have saved on my local disk, and then try to
save that copy on the network drive, the save is successful and OO does not
crash.  But if I then open the newly saved file from the network drive, make one
change and save, OO crashes again without the opportunity to submit a crash report.
Comment 2 grelarse 2010-02-07 09:13:59 UTC 
WORKAROUND:

/var/log/messages showed the following after an OO crash:

Feb  7 10:00:48 opus kernel: [31525.194663] Status code returned 0xc0000054
NT_STATUS_FILE_LOCK_CONFLICT
Feb  7 10:00:48 opus kernel: [31525.194704]  CIFS VFS: Send error in read = -13

So I switched off Oplocks in the NAS configuration screen and the crashes stopped.
Comment 3 Olaf Felka 2010-02-08 06:47:30 UTC 
looks like issue 107192

*** This issue has been marked as a duplicate of 107192 ***
Comment 4 Mechtilde 2010-03-04 18:39:43 UTC 
duplicate -> closed