<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Text is invisible, both in UI and in editor on update to 5.3.2, older AMD and Intel GPUs" href="https://bugs.documentfoundation.org/show_bug.cgi?id=107166#c139">Comment # 139</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Text is invisible, both in UI and in editor on update to 5.3.2, older AMD and Intel GPUs" href="https://bugs.documentfoundation.org/show_bug.cgi?id=107166">bug 107166</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to tomangelo from <a href="show_bug.cgi?id=107166#c138">comment #138</a>) > Still searching for a way to force OS to use only AMD discrete GPU, but I've > just discovered that switching to Power Saving mode for soffice.bin in AMD > Settings app fixes this issue. Switching to Based on Power Source mode still > makes text invisible, even without AC adapter connected to notebook Which is weird, in power saving mode (i.e. the dGPU is bypassed) the program should run exclusively on the Intel HD 5500 here--suggesting the "4624" driver is good for use on the iGPU? And instead it is the AMD dGPU R9 M375 that is causing the visual glitches? Which is not to say that we are not still doing something dodgy with our DirectWrite/GDI interactions, we probably are, but how are open source cross platform projects supposed to guard against system hardware/driver issues like these?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>