Is there a way to disable changing the background in GNOME?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
3
down vote
favorite
I am setting up Ubuntu 12.04 with Gnome3 for a computer lab. I don't want the users to be able to change the background of the computer. Is there a way to prevent this? Or to revert the background back when the computer reboots?
gnome 12.04 wallpaper
add a comment |Â
up vote
3
down vote
favorite
I am setting up Ubuntu 12.04 with Gnome3 for a computer lab. I don't want the users to be able to change the background of the computer. Is there a way to prevent this? Or to revert the background back when the computer reboots?
gnome 12.04 wallpaper
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I am setting up Ubuntu 12.04 with Gnome3 for a computer lab. I don't want the users to be able to change the background of the computer. Is there a way to prevent this? Or to revert the background back when the computer reboots?
gnome 12.04 wallpaper
I am setting up Ubuntu 12.04 with Gnome3 for a computer lab. I don't want the users to be able to change the background of the computer. Is there a way to prevent this? Or to revert the background back when the computer reboots?
gnome 12.04 wallpaper
edited Apr 23 '12 at 20:28
jippie
4,68821931
4,68821931
asked Apr 23 '12 at 14:05
nattlap
1612
1612
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
4
down vote
The new dconf
has options for lockdown and also has an example (where they use the wallpaper ;)) on the dconf system admin page:
Lockdown
Lockdown is supported by creating a 'locks' subdirectory in the keyfile directory (ie: /etc/dconf/db/local.d/locks). The files contained in this directory contain a list of keys to lock, one per line. Just as with the keyfiles, you may add any number of files to this directory. Here's an example of what one might look like:
# prevent changes to the company wallpaper
/org/gnome/desktop/background/picture-uri
Of course, you need to run the 'dconf update' tool after changing the locks. The tool will notice if the timestamp on the 'locks' directory has changed, so there is no need to touch the ".d" directory as well.
Presently (as of dconf 0.7.4) lockdown is only supported on a per-key basis. Put another way: you may not yet lock entire subpaths. This is for performance reasons, but there are plans to address this in future releases.
Thanks for the quick response. I will check it out and let you know.
â nattlap
Apr 23 '12 at 14:47
This is incomplete. It does not work if you don't use a custom profile to add a system db where to add lock keys. Look at my answer askubuntu.com/a/1034238/350004
â solsTiCe
May 10 at 9:46
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
The new dconf
has options for lockdown and also has an example (where they use the wallpaper ;)) on the dconf system admin page:
Lockdown
Lockdown is supported by creating a 'locks' subdirectory in the keyfile directory (ie: /etc/dconf/db/local.d/locks). The files contained in this directory contain a list of keys to lock, one per line. Just as with the keyfiles, you may add any number of files to this directory. Here's an example of what one might look like:
# prevent changes to the company wallpaper
/org/gnome/desktop/background/picture-uri
Of course, you need to run the 'dconf update' tool after changing the locks. The tool will notice if the timestamp on the 'locks' directory has changed, so there is no need to touch the ".d" directory as well.
Presently (as of dconf 0.7.4) lockdown is only supported on a per-key basis. Put another way: you may not yet lock entire subpaths. This is for performance reasons, but there are plans to address this in future releases.
Thanks for the quick response. I will check it out and let you know.
â nattlap
Apr 23 '12 at 14:47
This is incomplete. It does not work if you don't use a custom profile to add a system db where to add lock keys. Look at my answer askubuntu.com/a/1034238/350004
â solsTiCe
May 10 at 9:46
add a comment |Â
up vote
4
down vote
The new dconf
has options for lockdown and also has an example (where they use the wallpaper ;)) on the dconf system admin page:
Lockdown
Lockdown is supported by creating a 'locks' subdirectory in the keyfile directory (ie: /etc/dconf/db/local.d/locks). The files contained in this directory contain a list of keys to lock, one per line. Just as with the keyfiles, you may add any number of files to this directory. Here's an example of what one might look like:
# prevent changes to the company wallpaper
/org/gnome/desktop/background/picture-uri
Of course, you need to run the 'dconf update' tool after changing the locks. The tool will notice if the timestamp on the 'locks' directory has changed, so there is no need to touch the ".d" directory as well.
Presently (as of dconf 0.7.4) lockdown is only supported on a per-key basis. Put another way: you may not yet lock entire subpaths. This is for performance reasons, but there are plans to address this in future releases.
Thanks for the quick response. I will check it out and let you know.
â nattlap
Apr 23 '12 at 14:47
This is incomplete. It does not work if you don't use a custom profile to add a system db where to add lock keys. Look at my answer askubuntu.com/a/1034238/350004
â solsTiCe
May 10 at 9:46
add a comment |Â
up vote
4
down vote
up vote
4
down vote
The new dconf
has options for lockdown and also has an example (where they use the wallpaper ;)) on the dconf system admin page:
Lockdown
Lockdown is supported by creating a 'locks' subdirectory in the keyfile directory (ie: /etc/dconf/db/local.d/locks). The files contained in this directory contain a list of keys to lock, one per line. Just as with the keyfiles, you may add any number of files to this directory. Here's an example of what one might look like:
# prevent changes to the company wallpaper
/org/gnome/desktop/background/picture-uri
Of course, you need to run the 'dconf update' tool after changing the locks. The tool will notice if the timestamp on the 'locks' directory has changed, so there is no need to touch the ".d" directory as well.
Presently (as of dconf 0.7.4) lockdown is only supported on a per-key basis. Put another way: you may not yet lock entire subpaths. This is for performance reasons, but there are plans to address this in future releases.
The new dconf
has options for lockdown and also has an example (where they use the wallpaper ;)) on the dconf system admin page:
Lockdown
Lockdown is supported by creating a 'locks' subdirectory in the keyfile directory (ie: /etc/dconf/db/local.d/locks). The files contained in this directory contain a list of keys to lock, one per line. Just as with the keyfiles, you may add any number of files to this directory. Here's an example of what one might look like:
# prevent changes to the company wallpaper
/org/gnome/desktop/background/picture-uri
Of course, you need to run the 'dconf update' tool after changing the locks. The tool will notice if the timestamp on the 'locks' directory has changed, so there is no need to touch the ".d" directory as well.
Presently (as of dconf 0.7.4) lockdown is only supported on a per-key basis. Put another way: you may not yet lock entire subpaths. This is for performance reasons, but there are plans to address this in future releases.
answered Apr 23 '12 at 14:30
Rinzwind
196k25375508
196k25375508
Thanks for the quick response. I will check it out and let you know.
â nattlap
Apr 23 '12 at 14:47
This is incomplete. It does not work if you don't use a custom profile to add a system db where to add lock keys. Look at my answer askubuntu.com/a/1034238/350004
â solsTiCe
May 10 at 9:46
add a comment |Â
Thanks for the quick response. I will check it out and let you know.
â nattlap
Apr 23 '12 at 14:47
This is incomplete. It does not work if you don't use a custom profile to add a system db where to add lock keys. Look at my answer askubuntu.com/a/1034238/350004
â solsTiCe
May 10 at 9:46
Thanks for the quick response. I will check it out and let you know.
â nattlap
Apr 23 '12 at 14:47
Thanks for the quick response. I will check it out and let you know.
â nattlap
Apr 23 '12 at 14:47
This is incomplete. It does not work if you don't use a custom profile to add a system db where to add lock keys. Look at my answer askubuntu.com/a/1034238/350004
â solsTiCe
May 10 at 9:46
This is incomplete. It does not work if you don't use a custom profile to add a system db where to add lock keys. Look at my answer askubuntu.com/a/1034238/350004
â solsTiCe
May 10 at 9:46
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f124456%2fis-there-a-way-to-disable-changing-the-background-in-gnome%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password