<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> <span class="fn">Aron Budea</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - 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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Keywords</td>
<td>
</td>
<td>bibisectRequest
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - 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#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - 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:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> <span class="fn">Aron Budea</span></a>
</span></b>
<pre>If anyone who's affected could verify whether the bug is caused by the same
commit as <a class="bz_bug_link
bz_status_NEW "
title="NEW - Text is missing in dialogs in some remote desktop connections"
href="show_bug.cgi?id=107942">bug 107942</a>, that would be helpful. For this you need Cygwin,
bibisect-win32-5.4 bibisect repo (a few GBs), and to follow the steps below:
- install Cygwin, including git,
- clone bibisect-win32-5.4 repo from [1],
- do a 'git log --all --grep="a51b7a1c3a7e7cf7b0c733e1dec40288278c1884" ' to
find the commit corresponding to that source commit in the bibisect repo,
- do a 'git checkout <commit>' with the commit hash found previously, try to
repro the issue, which should occur,
- do a 'git checkout HEAD~1' to go back a single commit, then try to repro the
issue again, it should not occur this time.
For the unfamiliar, the bibisect repo contains binary builds for each source
commit to make triaging regressions a lot easier (further details are at [2].
[1] <a href="https://wiki.documentfoundation.org/QA/Bibisect/Windows#bibisect-win32-5.4">https://wiki.documentfoundation.org/QA/Bibisect/Windows#bibisect-win32-5.4</a>
[2] <a href="https://wiki.documentfoundation.org/QA/Bibisect">https://wiki.documentfoundation.org/QA/Bibisect</a></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>