Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2268149 ** Information from BlockerBugs App:
The votes have been last counted at 2024-03-11 14:16 UTC and the last processed comment was #comment-899797
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
The upstream issue notes this apparently can also break Wine applications. I'm on the fence about this, I'm not seeing a strong correlation to the "common application" clause in the given criteria, and I don't think performing an install or post install update is impacted so it can be fixed later.
FinalBlocker -1
How does this not fall under the "Window manager functionality" criterion? I believe it's an exact hit!
It says:
An example of a violation would be e.g. if a significant number of QT applications couldn't be resized (but they should be), or if all Java applications failed to display any content.
In this case, all Java apps fail to receive any keyboard input after window switching (which is covered by the criterion), i.e. the switch wasn't performed correctly.
I tested with CardManager from Fedora repos, I can confirm the problem. So I believe it really likely affects all apps.
CardManager
FinalBlocker +1
How does this not fall under the "Window manager functionality" criterion? I believe it's an exact hit! It says: An example of a violation would be e.g. if a significant number of QT applications couldn't be resized (but they should be), or if all Java applications failed to display any content.
Well, when you put it that way... :D
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F40 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.