Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2072462
Information from BlockerBugs App:
<img alt="2072462" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2072462" />
The votes have been last counted at 2022-04-11 09:09 UTC and the last processed comment was #comment-791645
To learn how to vote, see:
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)
It's annoying, but it doesn't prevent using the app. Not being able to add a connection would be a blocker to me.
Agree with Ben
In the state before the available update:
Once the update is pushed stable and only this remains, then FinalBlocker -1.
I guess we can most easily agree on that, in order to push the update stable.
I think we don't need to block on this anymore with the update fixing the imo most visible scenario of occurence.
I agree with the above, ideally every means of removal would work correctly, but I feel like the most common means of removal working is enough to make this not a blocker.
The update which improved things is now stable.
Based on the current votes:
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.
to comment on this ticket.