Description: [META] Skia library bugs Let's collect here all Skia's bugs Lubus, I CCed you to this META Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: -
For the record, here's the announcement: https://lists.freedesktop.org/archives/libreoffice/2019-November/083878.html For now Skia can be enabled by setting the following environment variable: SAL_ENABLESKIA=1 And it's only enabled for X11 'gen' and Windows VCL backends.
Folks, when posting issues against Skia rendering (Vulkan h/w, or software only), please post GPU and driver details for your system On Windows systems, os GPU and driver details can be found in a run of msinfo32.exe OS and system hardware on the system summary. GPU hardware and driver on the components -> display tab Simple select and copy/paste. This will be needed to work out blacklist for Skia rendering. Thanks! Stuart
For maintaining a blacklist of GPU and Vulkan driver pairings, will need the Vulkan reported 'deviceID', 'vendorID' and 'driverVersion' -- these will not be the same as the os reported GPU and Driver details we'd used for OpenGL issues. At the moment, they are not exposed for review from the LO Skia implementation. The realtechVR OpenGL Extensions Viewer [1] now provides a reporting module for Vulkan resources. After a run of rendering testing, clicking the submit button will generate a set of feature reports, including a "vkview" report that has the GPU's internal Vulkan details. Those will be needed when reporting issues for potential Blacklisting. =-ref-= [1] http://www.realtech-vr.com/home/glview
(In reply to V Stuart Foote from comment #3) > For maintaining a blacklist of GPU and Vulkan driver pairings, will need the > Vulkan reported 'deviceID', 'vendorID' and 'driverVersion' -- these will not > be the same as the os reported GPU and Driver details we'd used for OpenGL > issues. > > At the moment, they are not exposed for review from the LO Skia > implementation. > > The realtechVR OpenGL Extensions Viewer [1] now provides a reporting module > for Vulkan resources. After a run of rendering testing, clicking the submit > button will generate a set of feature reports, including a "vkview" report > that has the GPU's internal Vulkan details. Those will be needed when > reporting issues for potential Blacklisting. > > =-ref-= > [1] http://www.realtech-vr.com/home/glview Lubos added (https://gerrit.libreoffice.org/c/core/+/91980) this: "So just dump the info to <cachedir>/skia.log (where on Windows the <cachedir> should be AppData\Roaming\LibreOffice\4\cache)." I think we should say to bugreporters just to give us info from that file if they wrote a skia bug reprot
Both ways are acceptable as long as they provide the necessary Vulkan information and not things like the marketing version numbers.
Since version 7.6 and the fix for bug 155070, the Skia log can be copied from Tools ▸ Options... ▸ LibreOffice ▸ View.