Bug 2121873

Summary: Compile LXDM against GTK3
Product: [Fedora] Fedora Reporter: Artem S. Tashkinov <aros>
Component: lxdmAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: christoph.wickert, mtasaka
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lxdm-0.5.3-22.D20220831git2d4ba970.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-16 00:16:18 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:

Description Artem S. Tashkinov 2022-08-26 22:17:43 UTC
For some reasons LXDM which must perfectly support GTK3 is compiled against GTK2 in Fedora.

I wonder why and whether it could be fixed now that RedHat wants to get rid itself of GTK2.

Comment 1 Mamoru TASAKA 2022-08-26 22:44:56 UTC
I am going to with GTK2 for this package for now.

Comment 2 Fedora Update System 2022-09-11 06:37:36 UTC
FEDORA-2022-e431f6f740 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e431f6f740

Comment 3 Fedora Update System 2022-09-11 20:11:12 UTC
FEDORA-2022-e431f6f740 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e431f6f740`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e431f6f740

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2022-09-16 00:16:18 UTC
FEDORA-2022-e431f6f740 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.