Bug 115827 - manjaro:LibreOffice Version: 5.3.7.2.0+ Writer crashes upon start
Summary: manjaro:LibreOffice Version: 5.3.7.2.0+ Writer crashes upon start
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-18 14:49 UTC by jojo
Modified: 2018-02-21 09:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
strace (175 bytes, application/gzip)
2018-02-18 14:51 UTC, jojo 		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 jojo 2018-02-18 14:49:54 UTC 
Description:
Neither via double-clicking a file, nor by starting via terminal writer can be started

Steps to Reproduce:
Steps of reproduction:
1. open terminal
2. input $ soffice
> office opens
3. click the button "Writer Document" 
> Program crashes and closes

Actual Results:  
> Program crashes and closes

Expected Results:
Possibility to start typing text


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 5.3.7.2.0+
Build ID: 5.3.7-6.1
CPU Threads: 2; OS Version: Linux 4.9; UI Render: default; VCL: gtk3; Layout Engine: new; 
Locale: en-US (en_US.utf8); Calc: group


User-Agent: Mozilla/5.0 (X11; Linux i686; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 1 jojo 2018-02-18 14:51:06 UTC 
Created attachment 139975 [details]
strace
Comment 2 Aron Budea 2018-02-18 19:16:14 UTC 
That log file has some binary content when unzipped.

Additionally, version 5.3 is EOL, can you please try with 5.4 or preferably with 6.0?
Comment 3 jojo 2018-02-20 20:11:26 UTC 
Fixed probleme via removal of Java Runtime environment:

1. Open libreoffice (not writer)
2. Go to Tools > Options > LibreOffice/Advanced
3. Remove tick from Use a Java runtime environment
4. Confirm with OK
Comment 4 Xisco Faulí 2018-02-21 09:43:24 UTC 
Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.