Bug 129274 - FILEOPEN docx file cannot open
Summary: FILEOPEN docx file cannot open
Status: RESOLVED DUPLICATE of bug 104347
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:docx, regression
Depends on:
Blocks:
 
Reported: 2019-12-08 09:22 UTC by raal
Modified: 2019-12-09 11:36 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
gdb bt (23.63 KB, text/plain)
2019-12-08 09:52 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description raal 2019-12-08 09:22:03 UTC
Description:
file from bug 98823 https://bugs.documentfoundation.org/attachment.cgi?id=123770

Steps to Reproduce:
1. open file https://bugs.documentfoundation.org/attachment.cgi?id=123770


Actual Results:
LO cannot open file

Expected Results:
open file


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 raal 2019-12-08 09:23:39 UTC
This seems to have begun at the below commit.
Adding Cc: to Miklos Vajna  ; Could you possibly take a look at this one?
Thanks

bibisect-linux-64-5.3$  73c8b8ef61dc6bfb884ae43f013b509afeda9190 is the first bad commit
commit 73c8b8ef61dc6bfb884ae43f013b509afeda9190
Author: Jenkins Build User <tdf@pollux.tdf>
Date:   Thu Sep 29 17:09:10 2016 +0200

    source 1d1748d143ab4270a2ca1b5117852b1b1bb4c526

author	Miklos Vajna <vmiklos@collabora.co.uk>	2016-08-30 09:14:47 +0200
committer	Miklos Vajna <vmiklos@collabora.co.uk>	2016-08-30 08:40:30 +0000
commit 1d1748d143ab4270a2ca1b5117852b1b1bb4c526 (patch)
tree ed1939265de131d1338d2d26657459a0aa2825e6
parent 11cc9bdc21be241f2feb3ab4822d9d365dba4f96 (diff)
Related: tdf#44986 DOCX import: handle w:gridAfter by faking cells
Comment 2 Julien Nabet 2019-12-08 09:52:58 UTC
Created attachment 156405 [details]
gdb bt

On pc Debian x86-64 with master sources updated today, I could reproduce this.
Comment 3 Timur 2019-12-09 11:36:53 UTC
Same file, same regression, same bibisecter. Duplicate.

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