Hi,
On Fri, Apr 10, 2020 at 10:16 AM Olivier Fourdan <ofourdan(a)redhat.com>
wrote:
On Fri, Apr 10, 2020 at 9:29 AM Olivier Fourdan
<ofourdan(a)redhat.com>
wrote:
> On Fri, Apr 10, 2020 at 9:09 AM Adam Williamson <
> adamwill(a)fedoraproject.org> wrote:
>
>>
>> I think these do all look like the same problem. If we can verify a fix
>> for this, an FE is probably reasonable...
>>
>>
> Looks like I can reproduce locally, so this is not HW dependent (I mean,
> other than using an intel GPU).
>
> I'll run a bisection to see what broke it.
>
Well, we might be lucky one that one, it looks like using a current git
snapshot fixes the issue for me...
If you want to give it a try, I ran a scratch build here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=43186375
Please let me know.
Humm, there is actually no (relevant) change in the code we use for Fedora
between the two git snapshots.
However, I noticed the current package was built in february and therefore
was built against the xserver 1.20.6 (as this was what we had in Fedora at
the time) while we upgraded to 1.20.7 mid march and then 1.20.8 recently.
As a test, I just rebuilt the current package (no change in the code) and
it works fine here, no more crash:
https://koji.fedoraproject.org/koji/taskinfo?taskID=43188723
So, FWIW, it looks like it might be just a matter of rebuilding the current
package to fix the issue.
Please let me know how that build works for you.
Cheers
Olivier