Issue 125932

Summary:

Save File for particular documents will fail with Write Error message

Product:

Calc

Reporter:

Rainer Bielefeld <rainerbielefeld_ooo_qa>

Component:

save-export

Assignee:

AOO issues mailing list <issues>

Status:

CONFIRMED ---

QA Contact:

Severity:

Normal

Priority:

CC:

oliver.brinzing, rainerbielefeld_ooo_qa

Version:

3.4.0 Beta (OOo)

Target Milestone:

---

Hardware:

All

OS:

Windows 7

Issue Type:

DEFECT

Latest Confirmation in:

4.2.0-dev

Developer Difficulty:

---

Attachments:

Description	Flags
Sample Document	none

Description Rainer Bielefeld 2014-12-08 08:23:04 UTC

Created attachment 84281 [details]
Sample Document

Steps how to reproduce with WIN7 64 bit German AOO420m1(Build:9800)  -  Rev. 1630928:

1. Open attached sample document
2. Provoke a crash due to "Issue 125419 - Opening openxml files crashes"
   (simply try to open all documents from .zip simultaneously via AOO
   Files dialog)
3. Start Recovery until sample document will have been opened again
   > everything looks normal, may be you observe hectic flickering in
     Status bar
4. Do a minimum edit (type "y" into Tabelle1.R418 to replace the contents
   and press Enter)
   > now definitively hectic flickering in Status bar
5. Click Disk icon in Standard Toolbar to save document
   bug: after 10% Progress bar (or so) Error message "Error Saving document ..
        Write error
        Document could not be saved

No way to save document with different name or in different folder.

I already see the problem with a 3.4.0 dev version.

This one might be related to "Issue 120170 - (JA UI related?) Autosave loops and endlessly produces 0KB backup files when it fails to autosave", I also see thousands of 0kb copies of one of my affected documents in the backup folder.

Comment 1 Oliver Brinzing 2014-12-08 17:50:41 UTC

Comment 2 Oliver Brinzing 2014-12-08 19:06:43 UTC

confirming aoo401/win7 64bit - saving is not possible

already reproducible with oo32

crash produced with:

REM  *****  BASIC  *****
OPTION EXPLICIT
Sub Main
	Dim oDispatcher as Object
	Dim mNoArgs()
	oDispatcher = createUnoService("com.sun.star.frame.DispatchHelper")
	oDispatcher.executeDispatch(ThisComponent.getCurrentController().Frame, 
                                                   ".uno:crash", "", 0, mNoArgs())
End Sub

Comment 3 Rainer Bielefeld 2015-02-04 18:12:11 UTC

"After recovery" is a reliable way how to reproduce the problem, but it's not a necessary condition. I see the problem more or less every 4th use of affected documents, and it really drives me nuts, I now use LibO for spreadsheets as much as possible.