Bug 755363

Summary: Background config is resetted every time I log in, since last update
Product: [Fedora] Fedora Reporter: Juan <jfarre>
Component: gnome-backgroundsAssignee: David Zeuthen <davidz>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: davidz, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 13:41:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Juan 2011-11-20 22:27:11 UTC
Description of problem:
About half-an-hour ago, I installed the last updates for my Fedora installation. I'm using the default Gnome 3 desktop.
When I first logged in after the updates, The background image (the default Verne one) didn't appear filling the whole screen, as usual, but leaving some space in the sides. At the same time, a message appeared saying that the new version of gDesklets had a Float functionality, activated with Shift-F12.
I don't know if it has anything to do with this new version of gDesklets or it's totally independent, but I've changed the background image configuration to a different image filling the screen, and every time I log in again it gets resetted to the default image not filling the whole screen.

Version-Release number of selected component (if applicable):
gnome-backgrounds-3.2.0-1.fc16
desktop-backgrounds-gnome-16.0.0-1.fc16
gdesklets-0.36.3-2.fc15

How reproducible:
Since I upgraded the whole system with last stable versiosn, just have to change the background config, log out and log back in.


Steps to Reproduce:
1. Upgrade the gnome 3 system to last versions
2. Change background config
3. log out
4. log in
  
Actual results:
Background config is resetted to default image in a mode that does not fill the whole screen (I guess maintaining proportions)

Expected results:
Last background config stays as configured and is not resetted.

Additional info:

Comment 1 Juan 2011-12-11 00:39:42 UTC
wallpapoz-0.5-9 does not fix this problem (supposing there's any relationship with it...)

Comment 2 Fedora End Of Life 2013-01-16 13:01:20 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 13:41:03 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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