Bug 108096 - OpenGL output broken in LO 5.3, 5.4 (Linux, Intel graphics, Open GL 3.3, Mesa 12)
Summary: OpenGL output broken in LO 5.3, 5.4 (Linux, Intel graphics, Open GL 3.3, Mesa...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
5.3.3.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks: OpenGL-Linux
  Show dependency treegraph
 
Reported: 2017-05-25 21:59 UTC by Mikhail Novosyolov
Modified: 2018-07-17 10:46 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
video showing graphical artefacts (754.66 KB, video/mp4)
2017-05-25 21:59 UTC, Mikhail Novosyolov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Novosyolov 2017-05-25 21:59:51 UTC
Created attachment 133590 [details]
video showing graphical artefacts

$ libreofficedev5.4 --version
LibreOfficeDev 5.4.0.0.alpha1 0b9f9bef65bb21ebb6a64aafad448f7f62dc824a
$ libreoffice --version
LibreOffice 5.3.3.2 30m0(Build:2)

Turned on OpenGL output (did not disable OpenGL blacklist), got severe artefacts, attach a screencast showing artefacts. Both LO 5.3 and 5.4. Do not remember this issue with LO 5.1, e.g., but I'm not sure.

$ glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Desktop 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 12.0.6
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 12.0.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 12.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:


I got a not usable GUI, so, to revert the setting I had to edit
<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseOpenGL" oor:op="fuse"><value>false</value></prop></item>
in ~/.config/libreoffice/4/user/registrymodifications.xcu
Comment 1 Mikhail Novosyolov 2017-05-25 22:03:27 UTC
Upgraded the graphics stack and got NO difference

$ glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Desktop 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.1.0
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.1.0
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.1.0
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
Comment 2 Xisco Faulí 2017-05-26 11:33:05 UTC
Hello Mikhail,
Thanks for reporting this bug.
I think it's caused by the same root cause as in bug 107942.
Closing as RESOLVED DUPLICATED

*** This bug has been marked as a duplicate of bug 107942 ***
Comment 3 Mikhail Novosyolov 2017-05-26 11:35:52 UTC
Why do you think so? Does remote desktop use OpenGL output?
Comment 4 Xisco Faulí 2017-05-26 11:43:20 UTC
In bug 107942, it happens when using the remote connection, but it's doesn't it's only happening when using a remote connections. There's also a similar bug: bug 107166. Anyway, just to be sure this was introduced by the mentioned commit a51b7a1c3a7e7cf7b0c733e1dec40288278c1884, Could you please bisect it with bibisect-win32-5.4 ? You can find all the information here: https://wiki.documentfoundation.org/QA/Bibisect/Windows
Comment 5 Mikhail Novosyolov 2017-05-26 11:45:52 UTC
commit a51b7a1c3a7e7cf7b0c733e1dec40288278c1884 "forces uding GDI when needed", how is GDI (DirecX) in Windows connected with OpenGL in Linux? Sorry, I don't understand you.
Comment 6 Mikhail Novosyolov 2017-05-26 11:48:29 UTC
If bibisecting in Linux is needed, I can try doing it (have never done it before)
Comment 7 Xisco Faulí 2017-05-26 11:50:38 UTC
Ouch sorry, since hardware was set to All, I thought it was happening on Win, I didn't read the summary, my bad. Then, Could you please bisect it to see when it was introduced ? Info: https://wiki.documentfoundation.org/QA/Bibisect/Linux
Setting back to UNCONFIRMED
Comment 8 alexander-lo 2017-06-24 17:03:31 UTC
Hi! Just wanted to say that this affects me too:
Debian 9, Linux 4.9.0-3, MESA 13.0.6, X11, AMD Radeon R9 M280 with radeon driver

It's just the missing surfaces are "colorful" (visual noise, probably uninitialized memory) instead of just white. The issues started appearing after the recent upgrade from 5.2.7 to 5.3.4:
https://packages.qa.debian.org/libr/libreoffice/news.rss20.xml

I've did not recently change any graphic-acceleration related changes.
Comment 9 Xisco Faulí 2017-11-22 16:35:12 UTC
Hi Mikhail, Alexander,
is this issue still reproducible in the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
Comment 10 Xisco Faulí 2018-01-22 14:59:03 UTC
(In reply to Xisco Faulí from comment #9)
> Hi Mikhail, Alexander,
> is this issue still reproducible in the latest version of LibreOffice
> from https://www.libreoffice.org/download/libreoffice-fresh/ ?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 11 Buovjaga 2018-07-14 16:51:49 UTC
(In reply to Xisco Faulí from comment #9)
> Hi Mikhail, Alexander,
> is this issue still reproducible in the latest version of LibreOffice
> from https://www.libreoffice.org/download/libreoffice-fresh/ ?

Alexander was not in CC, so repeating question.
Comment 12 alexander-lo 2018-07-17 10:39:06 UTC
Using the Libreoffice from the Flatpak repo:
LibreOffice 6.0.5.2 54c8cbb85f300ac59db32fe8a675ff7683cd5a16

I do not see any issues anymore even if enabling both
`org.openoffice.Office.Common.VCL.UseOpenGL` and
`org.openoffice.Office.Common.VCL.ForceOpenGL` from advanced settings.

I think it's fixed.
Comment 13 Mikhail Novosyolov 2018-07-17 10:46:19 UTC
I also think so, but don't have that hardware anymore.