Bug 101387 - gtk/gtk3/opengl: render issues (white rectangles)
Summary: gtk/gtk3/opengl: render issues (white rectangles)
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-08 12:57 UTC by Gustav Ekner
Modified: 2018-03-02 10:06 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
white rectangles (24.65 KB, image/png)
2016-08-08 12:57 UTC, Gustav Ekner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gustav Ekner 2016-08-08 12:57:39 UTC
Created attachment 126670 [details]
white rectangles

Hi,

I have Ubuntu 16.04 with the default Libre Office installation (5.1.4.2). The problem is that in the toolbar, there are white rectangles everywhere (see attachment).

What makes the problem serious, is that when I go to Tools -> Options -> View, check "Use OpenGL for all rendering", and restart, the rectangles are gone. But when I do certain things, Libre Office will crash and the whole system will freeze. For example when I go to the Gallery side bar, drag an arrow to the document, and double click that arrow.

I have an AMD 7770 graphics card, and the standard open source x.org driver (which is the only one, because since from Ubuntu 16.04, support for the proprietary fglrx has been dropped).

I have also tried to install the snap version if libre office following your guide, and then I got the 5.2.0.4 version. At the same settings page, the "Use OpenGL for all rendering" option is gone, and it seems to be enabled, because Libre Office crashes and freezes the system the same way. Since I launched the snap version from the terminal, I could easily get the log: http://paste2.org/E1zsEVsb
Comment 1 Aron Budea 2016-08-10 23:53:01 UTC
I couldn't reproduce the graphical issues myself with 5.1.4.2 / Ubuntu 16.04 (VM).
Can you check if the artifacts are there if you start LibreOffice via "SAL_USE_VCLPLUGIN=gtk soffice" (or "gtk3" or "gen" instead of "gtk")?

Note that the crash/freeze in the snap version of 5.2.0.4 is the same kind of crash that was reported in bug 101377, so I'd expect it to be a different issue. And while it seems to freeze the system, you can recover by switching to a different screen, and killing LibreOffice from there.
If you're interested in testing with a regular build of 5.2.0.4, please install/parallel-install [1] it from the usual sources (libreoffice.org or PPA).

[1] https://wiki.documentfoundation.org/Installing_in_parallel/Linux
Comment 2 Gustav Ekner 2016-08-11 14:06:26 UTC
Hi,

I installed the regular version of the 5.2.0.4 build (non-snap) parallel, according to your link. But then I had the exact same issues as with the 5.1.4.2 version, i.e. artifacts, and when "Use OpenGL for all rendering" is checked, the whole system can crash. I also would like to point out that I couldn't switch virtual terminal (like ctrl+alt+F7). It seems the issue has nothing to to with the snap version.

"SAL_USE_VCLPLUGIN=gtk soffice" with "gtk" or "gtk3" did not make any difference, but with "gen", both bugs are gone! Another interesting thing is that I also tested with "kde" (instead of gtk), and then the artifact bug is gone but not the crashing bug. I don't know, but perhaps the bugs are two separate ones.

I also think it's important that someone else with a graphics card from the same series (7700 or at least 7000) with the open source driver, can test this.
Comment 3 Björn Michaelsen 2016-08-15 14:21:36 UTC
removing whiteboard snap, as per comment 2 this happens with TDF builds too. Likely generic gtk/gtk3 issue as using the X11 backend has no issues.
Comment 4 Aron Budea 2016-08-17 20:04:23 UTC
Bug 100981 was also reported with an AMD GPU, and has some similarities (including freeze when OpenGL enabled).
Comment 5 Aron Budea 2016-09-01 08:21:26 UTC
Hi Gustav, I got around trying this out a bit (I'm using an AMD APU with integrated GPU, and Ubuntu 16.04 with default drivers), and did not see graphical glitches, but I could reproduce the crash, and opened bug 101836 on it.
Comment 6 Jean-Baptiste Faure 2016-10-02 10:56:23 UTC
Hi Gustav,

> "SAL_USE_VCLPLUGIN=gtk soffice" with "gtk" or "gtk3" did not make any 
> difference, [...]

To be sure, you should try 
export SAL_USE_VCLPLUGIN="gtk3"
libreoffice

in a terminal. In my Ubuntu unless I export the environment variable, it has no effect.

Best regards. JBF
Comment 7 Gustav Ekner 2016-10-02 11:10:45 UTC
Hi Jean-Baptiste Faure,

I followed your suggestion, but gtk and gtk3 still makes no difference. "gen" works however, so I don't think there is a problem with export.
Comment 8 Xisco Faulí 2017-07-27 23:19:48 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2018-01-29 10:27:54 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2018-03-02 10:06:17 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-20180302