I can't reproduce this, so it's likely to be hardware-specific (a graphical driver problem). Also, it's likely not related to a private mode, but rather multi-window usage or something like that. Either case, I'm not completely sure if it falls into the basic functionality test, I don't have a strong opinion on it either way.

Feels too hardware specific to block on, though I can't view the Mesa bug currently.

FinalBlocker -1

I reproduced this on an AMD APU (different than the one reported originally):
https://bugzilla.redhat.com/show_bug.cgi?id=2391242#c13

This person talks about seeing it with an AMD Bonaire discrete GPU:
https://bugzilla.mozilla.org/show_bug.cgi?id=1986254#c37

Discussed at the 2025-09-15 (blocker / freeze exception) review meeting:

We agreed to postpone this one as the exact details of the problem are still not clear. We will continue working with upstream to clarify the issue for next week's meeting.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2025-09-15/f43-blocker-review.2025-09-15-16.00.txt

Pretty sure I have now seen it on my system with an RX6800XT (RDNA2). I'm decently convinced everything using the amdgpu DRM driver is affected. This comment makes it look like radeon does not show the same issue.

Yeah, I think 'all amdgpu hardware' is probably the scope here.

Sadly, I can reproduce. Its an annoying bug and indeed it causes a bad impression on everyone using this amd hardware, right from the live-iso.

FinalBlocker +1

This legitimately stopped me from being able to effectively work, so I agree it violates the default application functionality criteria, I think "all amdgpu hardware" is a big enough blast radius to qualify.

FinalBlocker +1
FinalFE +1

FinalBlocker +1

Given the range of hardware (likely) affected:
FinalBlocker +1

Finally, we might not punt it again.

FinalBlocker +1

FinalBlocker +1
We've got pretty solid data on this now and it definitely seems to affect all or most amdgpu hardware, we know it's a real bug, we have the cause more or less identified.
AGREED AcceptedFinalBlocker

The following votes have been closed:

• Accepted FinalBlocker (+6, 0, -0)
  • +1 by nielsenb, geraldosimiao, derekenz, kparal, lruzicka, adamwill

Release F43 is no longer tracked by BlockerBugs, closing this ticket.