Bug 2175224 - Cannot select default background with gnome-control-center
Summary: Cannot select default background with gnome-control-center
Keywords:
Status: CLOSED DUPLICATE of bug 2178172
Alias: None
Product: Fedora
Classification: Fedora
Component: f38-backgrounds
Version: 37
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Luya Tshimbalanga
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-03 15:36 UTC by Michael Catanzaro
Modified: 2023-03-14 15:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-14 14:41:00 UTC
Type: Bug


Attachments (Terms of Use)
Proof (1.66 MB, video/webm)
2023-03-03 15:37 UTC, Michael Catanzaro
no flags Details

Description Michael Catanzaro 2023-03-03 15:36:18 UTC
Description of problem: After upgrading to Fedora 38, the Fedora 38 default desktop background is not selectable in gnome-control-center even though it is installed.


Version-Release number of selected component (if applicable): f38-backgrounds-gnome-38.0.0-2.fc38, gnome-control-center-44~beta-3.fc38


How reproducible: Always


Steps to Reproduce:
1. Upgrade from Fedora 37 to Fedora 38 (I used GNOME Software)
2. Open System Settings
3. Try to set desktop background

Actual results: F38 background is missing


Expected results: F38 background is selectable


Additional info: I see no warnings or error messages when running gnome-control-center in a terminal. No clue why all other backgrounds work and only this one is missing. I do see the backgrounds for Fedora 32-37 (I guess that tells me how long ago I installed this system), plus the GNOME upstream backgrounds, plus Fedora Workstation backgrounds. It's only the F38 background that is missing.

Comment 1 Michael Catanzaro 2023-03-03 15:37:17 UTC
Created attachment 1947716 [details]
Proof

Comment 2 Michael Catanzaro 2023-03-14 14:41:00 UTC

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


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