Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2372978 ** Information from BlockerBugs App:
The votes have been last counted at 2025-09-18 23:11 UTC and the last processed comment was #comment-986494
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
I'm not seeing this running Beta on my laptop. I have seen it on my Raspberry Pi testing some Beta candidate composes. I would need a better sense for how widespread this is to block on it.
FinalBlocker 0
Discussed at the 2025-09-15 (blocker / freeze exception) review meeting:
We weren't able to reproduce this on a clean F43 Beta install in a quick test, so we want to punt to try to get more detail on when and why this issue happens.
https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2025-09-15/f43-blocker-review.2025-09-15-16.00.txt
FinalFE +1
I have been seeing this on my F43 quite frequently now, it produced over 3 millions lines in journalctl in an entire day, so I tend to be:
FinalBlocker +1
I can confirm I have seen this on my laptop several times today, significant number of entries in the journal. This is without the google-chrome repository enabled.
Yeah, having reproduced this it's pretty bad. FinalBlocker +1 AGREED AcceptedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F43 is no longer tracked by BlockerBugs, closing this ticket.