<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><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#c166">Comment # 166</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 <span class="vcard"><a class="email" href="mailto:bugzilla@braten.be" title="Terje Bråten <bugzilla@braten.be>"> <span class="fn">Terje Bråten</span></a>
</span></b>
<pre>(In reply to Buovjaga from <a href="show_bug.cgi?id=107166#c165">comment #165</a>)
<span class="quote">> Could those still affected by the issue do this:
>
> 1. Install this master build which has debug information:
> <a href="https://dev-builds.libreoffice.org/daily/master/Win-x86@39/current/">https://dev-builds.libreoffice.org/daily/master/Win-x86@39/current/</a>
> 2. Open the Windows command line
> 3. In the command line change directory to the program/ inside the master
> build install path
> 4. Run this command: set SAL_LOG=1
> 5. Still in the same command line, run LibreOffice with this command:
> soffice.exe 2>debug.txt
> 6. You can quit LibreOffice soon after launch as the problem is immediately
> there (the invisible text)
>
> This will write a lot of debug information to a text file called debug.txt
> in the program/ directory. You should then attach the debug.txt file to this
> bug and developers can look at it.</span >
I tried this, and the file debug.txt is 0 bytes long.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>