Download it now!
Bug 129062 (Skia) - [META] Skia library bugs
Summary: [META] Skia library bugs
Status: NEW
Alias: Skia
Product: LibreOffice
Classification: Unclassified
Component: graphics stack (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on: 132312 132681 133016 129064 129074 129076 129077 129120 129211 129280 129345 129416 129439 129546 129863 129865 129929 130051 130233 130430 130604 131287 131408 131419 131426 131543 131547 131579 131663 131696 131697 131705 131721 131753 131939 131952 132013 132051 132084 132115 132155 132197 132228 132241 132297 132323 132333 132334 132335 132367 132438 132439 132498 132529 132856 133152 133166 133208 133215 133246 133254 133275 133289 133339 133399
Blocks:
  Show dependency treegraph
 
Reported: 2019-11-27 15:59 UTC by Roman Kuznetsov
Modified: 2020-05-26 07:44 UTC (History)
4 users (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 Roman Kuznetsov 2019-11-27 15:59:07 UTC
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:
-
Comment 1 Aron Budea 2019-12-12 19:06:54 UTC
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.
Comment 2 V Stuart Foote 2020-03-30 14:19:32 UTC
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
Comment 3 V Stuart Foote 2020-04-09 15:52:03 UTC
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
Comment 4 Roman Kuznetsov 2020-04-10 22:00:18 UTC
(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
Comment 5 Luboš Luňák 2020-04-14 09:42:29 UTC
Both ways are acceptable as long as they provide the necessary Vulkan information and not things like the marketing version numbers.