Bug 1833020

Summary: Default background is not the same as the one offered in Gnome Settings
Product: [Fedora] Fedora Reporter: Peter Simonyi <rhbz>
Component: f32-backgroundsAssignee: Luya Tshimbalanga <luya_tfz>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: elep331, luya_tfz, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 16:12:32 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 Peter Simonyi 2020-05-07 16:38:06 UTC
Description of problem:
The gnome-shell-extension-background-logo extension (by default) only shows the Fedora wordmark over the default background picture.  But with the latest update that makes the default background available to select from Gnome Settings, the logo is not shown after re-selecting the default background.

Version-Release number of selected component (if applicable):
f32-backgrounds-gnome-32.2.2-1.fc32.noarch

How reproducible:
Always

Steps to Reproduce:
1. With a fresh user account, observe that the background is the f32 default and the "fedora" is in the lower right corner.
2. Open Gnome Settings -> Background.
3. Click on the default background offered in the grid of options.

Actual results:
The background appears the same, but the Fedora wordmark disappears.

Expected results:
Nothing should change: the Fedora wordmark should still be visible.

Additional info:
The problem is that the f32 background offered in the Gnome Settings grid is not the same as the default, though it looks the same.

The default background is 'f32.xml':
    $ gsettings reset org.gnome.desktop.background picture-uri
    $ gsettings get org.gnome.desktop.background picture-uri
    'file:///usr/share/backgrounds/f32/default/f32.xml'

But after clicking the f32 background in Gnome Settings, the background is 'f32.png':
    $ gsettings get org.gnome.desktop.background picture-uri
    'file:///usr/share/backgrounds/f32/default/f32.png'

Comment 1 Elep331 2020-06-23 12:56:39 UTC
I can confirm it, I have the same bug.

Comment 2 Luya Tshimbalanga 2020-08-19 00:44:52 UTC
(In reply to Peter Simonyi from comment #0)
> Description of problem:
> The gnome-shell-extension-background-logo extension (by default) only shows
> the Fedora wordmark over the default background picture.  But with the
> latest update that makes the default background available to select from
> Gnome Settings, the logo is not shown after re-selecting the default
> background.
> 

Sorry for the delay of answer. It turned out the functionality is not an issue but a features. To solve the problen:
- Open Extensions application
- Select "Background Logo" under built-in list
- Enable "Show for all backgrounds"

The Fedora logo should now be visible at the bottom right.

Comment 3 Peter Simonyi 2020-08-19 12:04:34 UTC
That is a good workaround, but I don't think it's a feature or working as intended.

I think that the Background Logo extension is supposed to put the Fedora logo over the default background (unless, as you describe, the "Show for all backgrounds" option is enabled).

1. Start with a fresh installation of Fedora.  The background is the default background and the background logo is shown.  This is as expected.
2. Change the background to something else.  The background is different and the logo is not shown.  This is also working as expected.
3. Now change the background back to the default.  I expect the state to return to step 1 (default background with logo), but instead the logo is still not shown.

This is because while the background image shown in steps 1 and 3 appears the same, the Background Logo extension compares the filenames and those are different.

The fresh installation of Fedora uses 'f32.xml' for the background.  But the "default" background option in the Gnome Settings panel sets the background to 'f32.png' instead of 'f32.xml'

Further note that you don't even have to do step 2 here: as described in my steps to reproduce in comment 0, from a fresh installation, just clicking on the default background makes the logo disappear.

The problem is that Gnome Settings is offering 'f32.png' as a background choice when it should be offering 'f32.xml'.

Comment 4 Fedora Program Management 2021-04-29 16:24:35 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2021-05-25 16:12:32 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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