Bug 119614 - Libreoffice Writer does not start (affects only Writer)
Summary: Libreoffice Writer does not start (affects only Writer)
Status: RESOLVED DUPLICATE of bug 108619
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.3.2 release
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-30 20:01 UTC by andi
Modified: 2018-09-24 07:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andi 2018-08-30 20:01:21 UTC
Description:
When starting writer, it might have an graphical issue and therefore does not start: upon start I can see the frame and then writer crashes

This bug affects only writer; in libreoffice 5. this issue was not around but since upgrade to libreoffice 6. I see this issur

Steps to Reproduce:
1.start writer (no matter how)
2.
3.

Actual Results:
crash and close libreoffice

Expected Results:
normal start of writer


Reproducible: Always


User Profile Reset: Yes



Additional Info:
I use a vintag system with a modern OS (Ubuntu 18.04, Mate)

my system:
IBM Thinkpad T43 (single core CPU, 1 GB RAM)
important the vintage screen resolution (this might affect the bug):
1024x768 px
Comment 1 andi 2018-09-01 20:44:52 UTC
I guess the bug described here is the same one:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1768306
Comment 2 Buovjaga 2018-09-23 17:11:15 UTC
(In reply to andi from comment #1)
> I guess the bug described here is the same one:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1768306

Do you mean it works for you after disabling Java like advised in the report?
If yes, we will closed as duplicate of bug 108619
Comment 3 andi 2018-09-23 20:33:28 UTC
yes, after disabling java the problem was solved.

Now I replace OpenJDK with Oracle JRE and can use java without crashing.

Conclusion: it might have something to do with OpenJDK and Java enabled.
Comment 4 Buovjaga 2018-09-24 07:04:41 UTC
Thanks.

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