Description of problem: When booting up Fedora 34 KDE Plasma on VMware Workstation 16 and VMware Fusion 11 and 12, I am not able to login to my Plasma session because SDDM crashes with Mesa 21. Version-Release number of selected component (if applicable): 21.0.0~rc5-1.fc34 How reproducible: Always Steps to Reproduce: 1. Install Fedora 34 KDE Plasma nightly in VMware 2. Reboot Actual results: System boots to a black screen (sddm-greeter crashes in the background) Expected results: System boots into SDDM, allowing login Additional info: If I manually downgrade to mesa-20.2.3-2.fc34, everything works again. It breaks with mesa 20.3 and newer.
Proposed as a Blocker for 34-beta by Fedora user ngompa using the blocker tracking app because: This bug violates the basic criterion for "Expected installed system boot behavior" where "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility". There is no way to log in or use the installed desktop.
Discussed during the 2021-02-22 blocker review meeting: [0] The decision to classify this bug as an "AcceptedFreezeException (Beta)" and delay the classification of this bug as we think this is serious enough to be an FE at least, but not sure yet if it's wide enough in impact to constitute a blocker. We are punting for more testing and also to look at fixing it. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-02-22/f34-blocker-review.2021-02-22-17.07.txt
Tentatively fixed with FEDORA-2021-25de318629.
Discussed during the 2021-03-01 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Beta)" was made as it was generally felt this isn't going to affect enough people to constitute a conditional violation of "must boot to a working desktop", and VMware is not covered by the virtualization criteria. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-03-01/f34-blocker-review.2021-03-01-17.01.txt
Neal, can you confirm whether it truly is fixed and close the bug if so? That update went stable a while ago. Thanks!
(In reply to Adam Williamson from comment #5) > Neal, can you confirm whether it truly is fixed and close the bug if so? > That update went stable a while ago. Thanks! Yes, this is fixed for me.