Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2009063 ** Information from BlockerBugs App:
Commented but haven't voted yet: adamwill
The votes have been last counted at 2021-10-04 15:30 UTC and the last processed comment was #comment-754574
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 FinalFE +1
The user will eventually get notified of updates. It's just not happening according to the expected timeframe. So yeah, it's a sad bug, but I don't think we need to block release over it.
There's already a fix on the way... https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1008
FinalFE +1
I'm inclined to vote +1 on blocker status, but it's not clear how long "eventually" is. If the user doesn't get notified for a day, that's one thing. If it's a week or more, that's something else.
The upstream PR has more details on when this goes wrong:
" 1. the suspend can delay the notification, depending whether the monotonic time moves on while the machine is suspended or not 2. there had been reset the last update notification timestamp in error after the updates had been received. "
I'm kinda with @bcotton , but based on the vote, this is:
AGREED RejectedFinalBlocker AGREED AcceptedFinalFreezeException
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.