Bug 2362756

Summary:	slick-greeter doesn't use default Fedora 42 background
Product:	[Fedora] Fedora	Reporter:	Greg Bailey <gbailey>
Component:	slick-greeter	Assignee:	leigh scott <leigh123linux>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	42	CC:	epel-packagers-sig, leigh123linux
Target Milestone:	---	Keywords:	Desktop, EasyFix, Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-04-28 20:32:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Greg Bailey 2025-04-28 17:51:18 UTC

After upgrading from a MATE desktop system running Fedora 41 to Fedora 42 using the system upgrade option, the default login screen has a black background and the Fedora 42 desktop background is not used.

The `/etc/lightdm/slick-greeter.conf` file references a default background of `/usr/share/backgrounds/default.png`, but this file does not exist. Instead, the `/usr/share/backgrounds` directory contains symlinks such as `default-dark.jxl`, `default.jxl`, and `default.xml`.

If I create a symlink `/usr/share/backgrounds/default.png` that points to `./f42/default/f42-01-day.jxl` (yes, this is a mismatched filetype), the background is shown. Or, I can provide a symlink that points to an older Fedora background that *is* in *png* format, which also works.

Can slick-greeter be adapted to support the JXL files that are included with Fedora 42?

Reproducible: Always

Steps to Reproduce:
1. Install MATE desktop with lightdm and slick-greeter-mate
2. Logout or reboot
3. Observe black background for the login page
Actual Results:
There is no background image on the login page

Expected Results:
Fedora 42 default background would be used for the login page

Comment 1 leigh scott 2025-04-28 20:32:35 UTC


*** This bug has been marked as a duplicate of bug 2354999 ***