[Libreoffice-bugs] [Bug 112305] Text is invisible, both in UI and in editor, AMD R5 and R7 drivers Windows 10

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=112305

V Stuart Foote <vstuart.foote at utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |109234

--- Comment #7 from V Stuart Foote <vstuart.foote at utsa.edu> ---
(In reply to Mike Kaganski from comment #6)
> ... improving the
> Safe Mode dialog so that it (1) should launch safely with regards of this
> issue, and (2) should provide an option to run LO with required settings to
> workaround this problem.

Not sure it is appropriate, or even feasible, to be handled in Safe Mode.
Especially if the failure is AMD hardware driver related for rendering DirectX
DirectWrite Direct2D text. Any Safe Mode work would have to signal the OS to
force non-accelerated CPU rendering, or alternatively force OpenGL rendering.

And this really seems a corner case for users afflicted with AMD GPUs and balky
DirectX and OpenGL drivers--it is not common.

Seems, if we can't get Direct2D rendering, then maybe forcing OpenGL rendering
for these modern R5/R7 AMD GPUs might be a better approach. May require we
figure out how to signal the OS to force AMD config to use OpenGL and force a
"high performance" rendering assignment for LibreOffice. That might not need to
be a Safe Mode fall back, and could be done as a "white listing" as part of the
OpenGL validation checks.

Very real issue is that we can't find reliable hardware configuration to
reproduce for WinDbg trace.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=109234
[Bug 109234] [META] DirectWrite rendering bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20170911/4cd30433/attachment-0001.html>