Bug 981509

Summary: Wallpaper options all disappear
Product: [Fedora] Fedora Reporter: Bob Agel <cragel>
Component: gsettings-desktop-schemasAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: debarshir, fmuellner, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 15:51:53 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 Bob Agel 2013-07-05 02:41:08 UTC
Description of problem: Using Gnome3 but added gnome-classic-session to test.  Once logged into Gnome-classic-session, wallpaper reverted to black (blank) and had to select one from the Settings > Background.  All optional backgrounds were present for my selection and selected one installed without a problem. Also, the options for Pictures and Colors were also present.  HOWEVER, when logging out and back into Gnome3, I again had a black backround and when I went to Settings > Background, there are no options or menu items available; no wallpapers, no buttons for pictures or colors either.

I am able to select my IMG_2131.JPG and 'set it as wallpaper' without incident just as I had before the incident, but "locate" only shows it in Pictures, no other location.  Surprisingly, If I switch pictures, then go back to the original, there's an alert: "Replace file IMG_2131.JPG?  Another file with the same name already exists in 'Wallpapers'.  Replacing it will overwrite it's content." and it shows the same pic.  So, "Settings > Background" has apparently lost it's way to the proper file.  


Version-Release number of selected component (if applicable):


How reproducible: Attempt to change wallpaper > fail.


Steps to Reproduce:
1. F19 DVD installation normal
2. Add gnome-classic-session
3. Lose wallpaper option on return to gnome3

Actual results: blank background instead of wallpaper, no option to add anything but own available jpegs.


Expected results: 


Additional info:

Comment 1 Fedora End Of Life 2015-01-09 18:40:47 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 2 Fedora End Of Life 2015-02-17 15:51:53 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.