Bug 136118 - Writer crashes when opening any DOCX
Summary: Writer crashes when opening any DOCX
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.3 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-25 17:56 UTC by Andrii Kyrylchuk
Modified: 2020-08-28 05:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
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 Andrii Kyrylchuk 2020-08-25 17:56:39 UTC 
Description:
When I open any docx file, LO crashes after a second or two. The same happens when I launch LO again and try to recover a docx file. Everything seems to work fine in Safe mode.



Steps to Reproduce:
1. Open a .docx file.


Actual Results:
The file contents shows for a second, then LO crashes.

Expected Results:
Correct opening of the document.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 7.0.0.3
Build ID: 7.0.0-1
CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Operating System: Arch Linux
Kernel: Linux 5.8.3-arch1-1
Architecture: x86-64
Comment 1 Julien Nabet 2020-08-25 18:54:02 UTC 
1) Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ?

2) Do you reproduce this if you do:
- launch terminal/console
- export SAL_USE_VCLPLUGIN=gen && soffice --writer
- open a docx
?

3) If you still reproduce this, would it be possible you attach a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Comment 2 Andrii Kyrylchuk 2020-08-27 20:09:53 UTC 
Dear Julien,

1) I am running the freshest version 7.0.0.3. My UI render is not OpenGL and the problem is not about the OpenCL, I guess. 
When I renamed my user profile the problem disappeared.
The problem was also gone in Safe mode with the old profile.
Unfortunately, I was not able to reproduce step 2 of your suggestions because after renaming my user profile back, the problem was already gone. 

So it seems that the problem was in a corrupted profile. Thank you for help and sorry for bothering!
Comment 3 QA Administrators 2020-08-28 04:04:51 UTC Comment hidden (obsolete)