Bug 2267124

Summary: sddm-greeter killed by SIGSEGV with mesa 24.0.0
Product: [Fedora] Fedora Reporter: Manfred Egger <megger>
Component: mesaAssignee: Neal Gompa <ngompa13>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 40CC: ajax, bskeggs, igor.raits, jexposit, jgrulich, j, kde-sig, lyude, m, ngompa13, pierluigi.fiorini, rdieter, rhughes, rstrode, tstellar, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-05-16 07:57:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl dump none

Description Manfred Egger 2024-02-29 21:28:08 UTC
Created attachment 2019508 [details]
journalctl dump

Description of problem:
The sddm-greeter crashes immediately after loading. 

Version-Release number of selected component (if applicable):
sddm-0.20.0-11.fc40 
mesa-24.0.0-2.fc40 
kernel-6.8.0-0.rc6.49.fc40 

How reproducible:
always reproducible 

Steps to Reproduce:
1. boot the system 
2. let sddm start

Actual results:
sddm-greeter crashes, black screen

Expected results:
sddm-greeter should display the login screen

Additional info:
Manually downgrading the mesa packages to 23.3.6-1.fc39 seems to resolves the problem. 

System info:
Fedora 40 KDE Spin
Radeon graphics card

Comment 1 Manfred Egger 2024-03-06 19:41:48 UTC
It seems this bug is related to an upstream bug [1] reported against mesa 24 which affects Radeon graphics cards. 
I applied the patch from the upstream bug report and did a local package rebuild with mesa 24.0.2. This resolves the issue for me.
Arch Linux uses the same patch in combination with mesa 24.0.2 [2].

[1] https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613
[2] https://gitlab.archlinux.org/archlinux/packaging/packages/mesa

Comment 2 José Expósito 2024-03-13 15:14:21 UTC
I opened a MR to solve it in Fedora: https://src.fedoraproject.org/rpms/mesa/pull-request/47

A MR has not being opened upstream to solve this issue. I'll keep an eye on the issue to update the patch if required.

Comment 3 Aoife Moloney 2025-04-25 10:18:58 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2025-05-16 07:57:05 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.