<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [META] Skia library bugs" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129062#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [META] Skia library bugs" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129062">bug 129062</a> from <a class="email" href="mailto:79045_79045@mail.ru" title="Roman Kuznetsov <79045_79045@mail.ru>"> Roman Kuznetsov</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=129062#c3">comment #3</a>) > 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] <a href="http://www.realtech-vr.com/home/glview">http://www.realtech-vr.com/home/glview</a> Lubos added (<a href="https://gerrit.libreoffice.org/c/core/+/91980">https://gerrit.libreoffice.org/c/core/+/91980</a>) 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</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>