After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 348435 - Lockdown support for background capplet
Lockdown support for background capplet
Product: gnome-control-center
Classification: Core
Component: Background
Other Linux
: Normal enhancement
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Reported: 2006-07-23 18:04 UTC by Rob Bradford
Modified: 2021-06-09 16:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Initial patch for lockdown support (6.23 KB, patch)
2006-07-23 18:05 UTC, Rob Bradford
needs-work Details | Review

Description Rob Bradford 2006-07-23 18:04:57 UTC
This patch is very similar to the one me and Thomas have been working on for the theme switcher. No rush since the support won't be added to pessulus until post-2.16.
Comment 1 Rob Bradford 2006-07-23 18:05:56 UTC
Created attachment 69429 [details] [review]
Initial patch for lockdown support
Comment 2 Rodney Dawes 2006-08-16 15:02:47 UTC
The capplet already supports lockdown by disabling the user to write to individual keys.
Comment 3 Rob Bradford 2006-08-16 15:57:01 UTC

I've reopened this bug since I think that the current solution can be improved upon:

(1) You don't give any feedback to the user. The HIG says you should do that.

(2) This isn't the way its done everywhere else in the desktop.

(3) This makes it very hard to integrate with Pessulus, we have a 1-1 mapping between a key and an option. We also intend to use the description. This makes the maintenance manageable.


Comment 4 Rodney Dawes 2007-01-08 16:38:59 UTC
The mapping isn't 1:1. There are multiple options within the background capplet. Currently each one of those can be locked down individually. The addition of this patch would mean that we have multiple lockdown solutions. We really only need to have ONE across the desktop. I don't see any rason to change this now. Is there an official "this is the ONE way to do it" announcement? I haven't seen any. I'm rejecting this patch for now. If the way to do lockdown gets cleared up, and a patch that only does it that one way, is presented, then we can get that in.
Comment 5 Allison Karlitskaya (desrt) 2011-06-04 13:55:35 UTC
This is still broken in the new panel.  Locking down the individual keys in dconf results in absolutely no feedback in the panel.  The panel actually allows you to move the selection to a different background -- and simply nothing happens.

It should grey out and give a description of why (or something?).
Comment 6 Jeremy Bicha 2011-09-12 02:31:20 UTC
I agree with desrt. gnome-control-center should recognize that the background key is locked and change the Background panel accordingly. I think it should also be smart enough to tell if the user is an admin user and adjust based on whether the user likely has the ability to break the lock or not.
Comment 7 André Klapper 2021-06-09 16:02:11 UTC
GNOME is going to shut down in favor of
As part of that, we are mass-closing older open tickets in
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
and create a new enhancement request ticket at

Thank you for your understanding and your help.