Bug 104578

Summary: FILEOPEN DOCX: broken document getting worse
Product: LibreOffice Reporter: Telesto <telesto>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal Keywords: bibisectRequest, filter:docx, regression
Priority: medium    
Version: 3.5.7.2 release   
Hardware: All   
OS: All   
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=55160
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Layout LO3572
Layout LO4003
Layout LO4463
Layout LO5400Alpha
File in MS Word Viewer

Description Telesto 2016-12-11 12:27:16 UTC 
Description:
File import as report in bug 55160 is going backwards

Steps to Reproduce:
1.Open attachment 67460 [details] with different LibO versions for example: 3.3.0.4 ; 3.5.7.2 ; 4.4.6.3 ; 5.4.0.0.alpha0+ (bug 55160)


Actual Results:  
Layout is getting worse

Expected Results:
Layout should get better


Reproducible: Always

User Profile Reset: No

Additional Info:
File opens relatively OK with: 
LibreOffice 3.5.7.2 
Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b

But surely not in:
Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)

or

Version: 5.4.0.0.alpha0+
Build ID: 84f2ff67a7e404febf710b1dc7f66d06745c503f
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2016-12-09_23:20:01
Locale: nl-NL (nl_NL); Calc: CL



User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Comment 1 Telesto 2016-12-11 12:27:46 UTC 
Created attachment 129489 [details]
Layout LO3572
Comment 2 Telesto 2016-12-11 12:28:10 UTC 
Created attachment 129490 [details]
Layout LO4003
Comment 3 Telesto 2016-12-11 12:28:27 UTC 
Created attachment 129491 [details]
Layout LO4463
Comment 4 Telesto 2016-12-11 12:28:52 UTC 
Created attachment 129492 [details]
Layout LO5400Alpha
Comment 5 Telesto 2016-12-11 12:31:26 UTC 
Created attachment 129493 [details]
File in MS Word Viewer
Comment 6 MM 2016-12-11 14:46:22 UTC 
Your report is basically a dup from bug 55160.
Why not add some data in that report instead ?!
Comment 7 Telesto 2016-12-11 14:58:22 UTC 
(In reply to MM from comment #6)
> Your report is basically a dup from bug 55160.
> Why not add some data in that report instead ?!

<Telesto> Is a broken document getting worse also a regression?
<@buovjaga> Telesto: yes, it is worth bibisecting
<Telesto> Should I add it to the existing bug report or create a new one?
<@buovjaga> Telesto: hmm.. that's a tough one. I guess if it's breaking somewhere else than the original report was about, create a new one
<@buovjaga> Telesto: maybe it's best in any case to do a new report as the bibisectrequest would be confusing otherwise
Comment 8 MM 2016-12-11 15:59:43 UTC 
(In reply to Telesto from comment #7)
> (In reply to MM from comment #6)
> > Your report is basically a dup from bug 55160.
> > Why not add some data in that report instead ?!
> 
> <@buovjaga> Telesto: hmm.. that's a tough one. I guess if it's breaking
> somewhere else than the original report was about, create a new one

Could be, but that example isn't broken again, because it's not fixed in the first place. So it can't be a regression.
Comment 9 Telesto 2016-12-11 16:44:32 UTC 

*** This bug has been marked as a duplicate of bug 55160 ***