Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2042877 Information from BlockerBugs App: <img alt="2042877" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2042877" />
Commented but haven't voted yet: coremodule, geraldosimiao, kparal
The votes have been last counted at 2022-02-14 19:33 UTC and the last processed comment was #comment-781409
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
Discussed during the 2022-02-07 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as other testers have not immediately been able to reproduce this. We will ask lnie for more details on the scenario and try again to reproduce.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-07/f36-blocker-review.2022-02-07-17.00.txt
Fedora-Workstation-Live-x86_64-36-20220209.n.0.iso seems to be doing fine
It seems this is not replicable anymore at the branched F36 build. Must see if its at Fedora-Rawhide-20220127.n.0 too, if so, it is a Rawhide only bug, and not a F36.
Just tested Fedora-Rawhide-20220127.n.0 and it behaves just like Inie described. So I turned back again to the Fedora-Workstation-Live-x86_64-36-20220209.n.0.iso VM who was succesfully installed to search for a coredump manually (since I do not have the ABRT warning the firs time I installed the system, and I FOUND A COREDUMP FROM THE SAME COMPONENT. I'll attached it to the ticket. Strangely, I installed and runned this VM the first time without any crash warnings, the coredump still there, but the system is running fine.
@geraldosimiao Thanks for testing, but please add your testing results to bugzilla and not here. This ticket is just for discussing the blocker status. Thanks.
@kparal ok, no problems, already added to the ticket.
FinalBlocker +1
Seems reproducible now. Violates the crash notification critera.
AGREED AcceptedFinalBlocker
Discussed during the 2022-02-14 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:
"There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop".
It's not entirely clear whether this crash always triggers a notification but it seems to happen often enough to accept this.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-14/f36-blocker-review.2022-02-14-17.01.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.