Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1931070 - sddm crashes with mesa-21 on VMware
Summary: sddm crashes with mesa-21 on VMware
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 34
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException RejectedBlocker
Depends On:
Blocks: F34BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2021-02-20 13:36 UTC by Neal Gompa
Modified: 2021-03-12 15:48 UTC (History)
14 users (show)

Fixed In Version: mesa-21.0.0~rc5-2.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-12 15:48:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1921523 0 unspecified CLOSED sddm-greeter crashes in VMware Fusion or VMware Workstation when hypervisor 3D acceleration is enabled 2022-05-16 11:32:56 UTC

Description Neal Gompa 2021-02-20 13:36:20 UTC 
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.
Comment 1 Fedora Blocker Bugs Application 2021-02-20 13:41:04 UTC 
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.
Comment 2 Geoffrey Marr 2021-02-22 20:02:58 UTC 
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
Comment 3 Neal Gompa 2021-02-23 14:04:45 UTC 
Tentatively fixed with FEDORA-2021-25de318629.
Comment 4 Geoffrey Marr 2021-03-01 21:17:32 UTC 
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
Comment 5 Adam Williamson 2021-03-12 01:03:46 UTC 
Neal, can you confirm whether it truly is fixed and close the bug if so? That update went stable a while ago. Thanks!
Comment 6 Neal Gompa 2021-03-12 15:48:28 UTC 
(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.
Note You need to log in before you can comment on or make changes to this bug.