Bug 1374277 - gnome background change is not persistent
Summary: gnome background change is not persistent
Keywords:
Status: CLOSED DUPLICATE of bug 1366766
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-settings-daemon
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rui Matos
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-08 11:44 UTC by Oliver Ilian
Modified: 2017-07-03 15:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-09 08:08:18 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Oliver Ilian 2016-09-08 11:44:49 UTC
Description of problem:
If the Gnome background is set globally in /etc/dconf/db/local.d , a user configured background is overwritten with the globally set background.

Version-Release number of selected component (if applicable):
gnome-settings-daemon-3.14.4-12.el7.x86_64

Steps to Reproduce:
1. create the file /etc/dconf/db/local.d/00-global_settings
2. add the following lines to the file

[org/gnome/desktop/background]
picture-uri='Path to the background'


3. ensure you see the background
4. as user choose a new background via Settings - Background
5. log out and log back in as user

Actual results:
Global background is shown again.

Expected results:
User selected background should be shown.

Additional info:
Also after you logged in as user and you see the global background again, changing the background again shows the previous user selected background in the preview and also the path in dconf org/gnome/desktop/background shows the correct user chosen background.

It seems like the global setting is dominating here, however the user setting should dominate.

I also checked that there is no file in /etc/dconf/db/local.d/locks/ setting a background

This was working on RHEL 7.1 so this is a regression


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