Bug 104583 - add VMWare SVGA 3D graphics driver > 8.15.1.48 to blacklist for OpenGL usage on Windows
Summary: add VMWare SVGA 3D graphics driver > 8.15.1.48 to blacklist for OpenGL usage ...
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
5.2.3.3 release
Hardware: All Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Graphics-Card Virtual-Machine VCL-OpenGL
  Show dependency treegraph
 
Reported: 2016-12-11 15:39 UTC by steve
Modified: 2020-08-28 12:02 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
opengl_device.log (301 bytes, text/plain)
2016-12-11 15:40 UTC, steve
Details
win 10 opengl not a good idea (40.77 KB, image/jpeg)
2016-12-11 15:40 UTC, steve
Details

Note You need to log in before you can comment on or make changes to this bug.
Description steve 2016-12-11 15:39:31 UTC
Description:
Learned that blank icons and black boxes in LO under windows can have OpenGL usage as a cause. In order to prevent LO having such a horrible start on a first run on windows, I am adding the opengl_device.log + sscreenshot.

This happend under a win10 vm. So hope LO can add the graphics driver to the blacklist for OpenGL usage and / or detect it is being run in a vm and thus not use OpenGL.

Steps to Reproduce:
1. Installed LO fresh stable 5.2.3.3 in a win10 vm
2. opened writer, typed a few words and tried to save the file
3. ended up unable to save the file, and LO showing a black box and almost all icons where blank

Actual Results:  
black boxes for dialogs and icons blank and then jumping around. Really funny, but not a good way to get work done.

Expected Results:
LO should not show black boxes for dialogs and it's icons should be constantly displayed.


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/20100101 Firefox/50.0
Comment 1 steve 2016-12-11 15:40:09 UTC
Created attachment 129500 [details]
opengl_device.log
Comment 2 steve 2016-12-11 15:40:23 UTC
Created attachment 129501 [details]
win 10 opengl not a good idea
Comment 3 steve 2016-12-11 15:51:07 UTC
works fine w OpenGL disabled
Comment 4 Dennis Roczek 2016-12-11 15:51:42 UTC
@mmeeks: put it on the blacklist. :-p
Comment 5 V Stuart Foote 2016-12-11 19:57:41 UTC
Yes agree adding the VMWare SVGA 3D driver at 8.15.1.48 driver on blacklist is appropriate.

But also beleive we have an issue with support for OpenGL "Core profile" that came in with the 5.2 builds.

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2139606

Issues vanish by disabling OpenGL rendering--which the black list would do.

Or by setting the SVGA_VGPU10 environment variable to 0
(a regedit session on the VM, setting value of 0 for 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment\SVGA_VGPU10) as in the vmware tech note--and using
"compatibility profile"

Setting the SVGA_VGPU10 varaible makes OpenGL rendering with the
8.15.1.48 driver in the 5.1.3.2 build stable again. 

But with it set the 5.2.3.3 and 5.3.0beta2 builds will not honor the Tools -> 
View -> Use OpenGL rendering setting.  And if forced into OpenGL mode, they are 
very unstable with multiple crash restarts and zombied soffice.bin instances in Task Manager. 

On Windows 7 Ent (32-bit) guest VM on VMWare 12
was solid in 5.1.3.2 (644e4637d1d8544fd9f56425bd6cec110e49301b) with VMWare DriverVersion: 8.15.1.32
DriverDate: 7-15-2015
DeviceID: PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00
AdapterVendorID: 0x15ad
AdapterDeviceID: 0x0405
AdapterSubsysID: 0x040515ad
DeviceKey: System\CurrentControlSet\Control\Video\{AE721109-008D-41C0-8AE5-776DA1487993}\0000
DeviceString: VMware SVGA 3D

but on updating driver (via VMWare tools update in the guest OS) 
start having issues in OpenGL with 5.1.3.2
DriverVersion: 8.15.1.48
DriverDate: 7-12-2016
DeviceID: PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00
AdapterVendorID: 0x15ad
AdapterDeviceID: 0x0405
AdapterSubsysID: 0x040515ad
DeviceKey: System\CurrentControlSet\Control\Video\{AE721109-008D-41C0-8AE5-776DA1487993}\0000
DeviceString: VMware SVGA 3D

same issues in Version: 5.2.3.3
Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf
CPU Threads: 4; OS Version: Windows 6.1; UI Render: GL; 
Locale: en-US (en_US); Calc: group

same issues in Version: 5.3.0.0.beta1+
Build ID: 85c8695677fbf7162857410213f9ae1a1a8a371b
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; 
TinderBox: Win-x86@62-merge-TDF, Branch:libreoffice-5-3, Time: 2016-12-08_15:28:35
Locale: en-US (en_US); Calc: group
Comment 6 V Stuart Foote 2016-12-11 20:16:04 UTC
This needs to be checked against a Windows 8.1 and/or Windows 10 VM guest as it is not clear if the support of "Core profile" and "Compatibility profile" is impacted by the VM Operating system and possibly capability of the GPU driver on the host OS.

My testing thus far was on a Windows 10 Host with an nVidia GPU (Driver Version	21.21.13.7270)

But, it does suggest we have some additional issues with OpenGL support.
We could have similar driver OpenGL profile issues with VirtualBox and even Parallels host/guest combinations.

Might all need blacklist, but at least some mention in release notes and Wiki?
Comment 7 QA Administrators 2018-10-18 02:48:39 UTC Comment hidden (obsolete)
Comment 8 Buovjaga 2020-08-28 12:02:54 UTC
As Skia with Vulkan will replace OpenGL UI rendering on all platforms, it does not make sense to keep OpenGL UI reports open.

Details about Skia: https://www.collaboraoffice.com/success-story/implementing-vulkan-capable-libreoffice-user-interface-using-the-skia-library/