Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2178311 Information from BlockerBugs App: <img alt="2178311" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2178311" />
The votes have been last counted at 2023-03-15 13:34 UTC and the last processed comment was #comment-846906
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
FinalBlocker +1
So, I have at first voted for this to be a blocker, yet I am not able to reproduce it anyhow and I can only see the bug in openQA where it happens as described. However, in a local VM it works normally and I am seeing the notifications without any problems.
The impact of this issue is, for me, limited to openQA and thus not blocker worthy.
FinalBlocker -1
Can't reproduce it on my machine either. I'm open to +1 if we learn it's more widespread.
Alright, I tried to reproduce this on a Fedora-KDE-Live-x86_64-38-20230301.n.0.iso installed on VM and notifications show up the way it should, so perhaps some problem with openQA or the test case used? I'll change my vote.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F38 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.