Bug 146960 - FILESAVE DOCX: Write Error. The file could not be written.
Summary: FILESAVE DOCX: Write Error. The file could not be written.
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-24 12:12 UTC by Telesto
Modified: 2022-01-24 12:18 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Example file (89.16 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-01-24 12:13 UTC, Telesto 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2022-01-24 12:12:58 UTC 
Description:
FILESAVE DOCX: Write Error. The file could not be written.

Steps to Reproduce:
1. Open the attached file
2. Right click cupcake with raspberry (picture 6 in the navigator) and change anchor to 'to character'
3. Right click the blue cupcake (picture 5 in the navigator) and change anchor to 'to character'.
4. File Save as DOCX -> Write error

Actual Results:
Write error

Expected Results:
Writing the file (it works for DOC)


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 4a388f5e01ebb5a512931d11e48c4380382239c8
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2022-01-24 12:13:14 UTC 
Created attachment 177744 [details]
Example file
Comment 2 Telesto 2022-01-24 12:16:26 UTC 
Hmm.. strange no issue with
Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 587c530d13a5427ea6610d68d3db3fde27f50725
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 3 Telesto 2022-01-24 12:18:23 UTC 
Apparently a profile issue