Bug 116185 - LibreOffice does not start, icons too large
Summary: LibreOffice does not start, icons too large
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.1.6.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-04 15:59 UTC by Thomas Waldmann
Modified: 2018-11-05 16:12 UTC (History)
1 user (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 Thomas Waldmann 2018-03-04 15:59:35 UTC
Description:
Having same or similar "icons too large" issue as there, libreoffice does not
start:

https://askubuntu.com/questions/753020/loo-dont-start-gdk-warning-gdk-window-set-icon-list-icons-too-large

This started 2018-01 after a ubuntu trusty 14.04 -> xenial 16.04 upgrade.

Before, LO worked, afterwards "icons too large", does not start any more.

Interestingly, that strange hint from that URL worked:

vi ~/.config/libreoffice/4/user/extensions/bundled/lastsynchronized
and replace the 1 inside by a 0 (zero).

So, "problem fixed", I thought.

Now, 2018-02 (still xenial with current updates), LO suddenly stopped working
again and only says "icons too large" when invoked from a terminal but does
not start.

It gets even more strange now:

I checked the file and the 0 (that fixed the issue last time) is still
in there. So I just thought "what happens if I change it back to 1?", did
that and it worked. Changed it back to 0, still works.

One month later: it stopped working again. WTF?

So, could somebody please look into what's happening there, it is very
annoying if stuff just suddenly stops working for no apparent reason.

I'ld like to get it working there without having to apply voodoo-like spells
from remote.

I've never seen that strange effect on any other Linux machine.

Note: before I found that strange lastsynchronized stuff, I also tried killing
.config/libreoffice completely, that did not help.

Version that worked in the past:
trusty (14.04LTS) 4.2.8-0ubuntu5.3 [security]: amd64 i386

Problematic version:
xenial (16.04LTS) 5.1.6~rc2-0ubuntu1~xenial3 [security]: amd64 i386


Steps to Reproduce:
see above.

Actual Results:  
It is impossible to use LO, it does not start.

Expected Results:
Normal startup of LO.


Reproducible: Sometimes


User Profile Reset: Yes



Additional Info:
The hardware is relatively old AMD Athlon X2 or so with AMD/ATI graphics.

I currently don't know whether OpenGL is enabled, it is not my machine and I don't have easy access to it.


User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Comment 1 Buovjaga 2018-03-10 17:36:24 UTC
Could you try an appimage of the current "Fresh" version (6) https://www.libreoffice.org/download/appimage and see what happens?
Comment 2 QA Administrators 2018-10-09 11:26:27 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2018-11-05 16:12:35 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20181105