#2099 [kwin] Raspberry Pi 4 KDE fails to boot into GUI without nomodeset on 4K KVM | rhbz#2456896
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2456896 **
Information from BlockerBugs App:
2456896

Current vote summary

Commented but haven't voted yet: lruzicka

The votes have been last counted at 2026-04-13 18:27 UTC and the last processed comment was #comment-1010986

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)


FinalBlocker +1

FinalBlocker +1

FinalBlocker +1

Clear violation of https://fedoraproject.org/wiki/Basic_Release_Criteria#Expected_installed_system_boot_behavior

FinalBlocker +1

Apparently F43 already shipped like this?

I don't have a 4K monitor to test with, but it boots fine with my 1440p monitors. It does feel like a violation of the above boot criteria, but I could seem some kind of hardware specificity exemption argument being made.

FinalBlocker +1

FinalBlocker -1

Personally I don't think this is a blocker, it's actually working, just having issues with a particular monitor setup.

AGREED RejectedFinalBlocker

Discussed at the 2026-04-13 (blocker / freeze exception) review meeting:

It seems like this issue is not a general problem affecting all Pi 4s and all 4K displays, but rather a specific problem between kwin and some strange EDID data from the tested KVM switch. Consequently, the bug is rejected.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-04-13/f44-blocker-review.2026-04-13-16.00.log.txt

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F44 is no longer tracked by BlockerBugs, closing this ticket.

Metadata