Created attachment 101153 [details]
File has a link to local file
Steps to reproduce:
1. Open the file in LO
2. Save as docx
3. Open the file in MSO
RT file appears to be corrupt. MSO reports file corruption while opening the file.
One should be able to open RT without any error messages.
Operating System: All
Version: 18.104.22.168.alpha0+ Master
retested with 22.214.171.124.alpha0+ under Win7x64
Build ID: 2d6dacc1c93bfd4a9086f8fde6b0edbfdeb573c9
TinderBox: Win-x86@42, Branch:master, Time: 2014-10-13_23:44:09
roundtrip file can be opened by Docx readed with no corruption alert.
please retest with recent master and MS Word and give update of the bug status which I temporarily set to NEEDINFO
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
I reproduce the bug with LibreOffice 4.3.3 and 126.96.36.199.alpha1+
Build ID: bcbf45d9f94d177c6841ccede3ff0ba69c4f22b1
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-05-04_03:51:16
When I open the saved file in MS Word Viewer or MS Word 2010 I get a message that the file is corrupted.
After saving in LibreOffice 3.5.4 MS Word Viewer still shows error message, but MS Word 2010 opens the file. So, I set regression keyword.
Tommy, what program did you use to check the file after roundtrip?
Umesh Kadam, do you still want to have the bug assigned to you?
(In reply to Alexandr from comment #3)
> Tommy, what program did you use to check the file after roundtrip?
I used a freeware tool called Docx reader.
however a more accurate test has to be done with MS Word which I don't have
Problem still present in
Build ID: 1b1a90865e348b492231e1c451437d7a15bb262b
Locale: es-ES (es_ES)
on Windows 7 (64-bit) with Office 2010
Migrating Whiteboard tags to Keywords: (filter:docx bibisectRequest)
I'm setting this ticket back to NEW as it has been inactive for more than 3
Feel free to assign it back to you if you're still working on this.
This doesn't seem to be a regression. I've just tested it in
Build ID: eadc132d5fa339b6fe5b2f8bb482ed30dbd2314
which is the build from 2014-10-13 as in comment 1 and the file is corrupted when it's opened in office 2010.
Removing keywords bibisectRequest and regression
Open XML SDK 2.5 fails to open it saying: Cannot open the file: Invalid Hyperlink: Malformed URI is embedded as a hyperlink in the document
Have you tried to change security level?
Does it helps?
Application for fixing word documents
(In reply to Bartosz from comment #10)
> Have you tried to change security level?
> Does it helps?
> Application for fixing word documents
Anyway, LibreOffice is doing something wrong at export time. The original file can be opened by MSO without problem, the roundtripped file not.
Build ID: fa89a464ca9c76332f533da0ab641da5acd00b52
CPU threads: 1; OS: Windows 6.1; UI render: default;
TinderBox: Win-x86@39, Branch:master, Time: 2017-05-19_01:24:56
Locale: es-ES (es_ES); Calc: group
@Bartosz, Are you planning to work on this?
Reproduced with LO 5.4.3
It seems that issue is caused by wrong relationship entry in file: word/rels/document.xml.rels
The entry which is causing issue is:
<Relationship Id="rId2" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/hyperlink" Target="file:///G:%3FChromium.Htm" TargetMode="External"/>
Issue no longer reproduced in
Build ID: 495ac1bc97f3deea8e13cb1a2b9f59d087873c3f
CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3;
Locale: en-US (ca_ES.UTF-8); Calc: group threaded
closing as RESOLVED WORKSFORME
[Improvement found by office-interoperability-tools]