Bug 2362756 - slick-greeter doesn't use default Fedora 42 background
Summary: slick-greeter doesn't use default Fedora 42 background
Keywords:
Status: CLOSED DUPLICATE of bug 2354999
Alias: None
Product: Fedora
Classification: Fedora
Component: slick-greeter
Version: 42
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: leigh scott
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-28 17:51 UTC by Greg Bailey
Modified: 2025-04-28 20:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-04-28 20:32:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.